I am a newbie in Infopath & Sharepoint. I am trying to create a form from Infopath 2013 and publish it as a document library to Sharepoint. I have some 60 fields that needs to be calculated(add) into another field. When tried to use the Design Checker, it throws an error as mentioned below in the screenshot. But it accepts if I key in only 45 fields in the Insert Formula text area. Is there any limitation on number of fields to be entered in Insert Formula? When I use PREVIEW in Infopath it works fine. This error pops up only when I try to publish it to Sharepoint. Any ideas on how to resolve this? - Thanks inadvance
InfoPath preview is rendered with IP Filler. The Browser experience has always been different, and the Filler preview is not a reliable check for the browser experience. You may have hit the limits of what a browser form can do. I don't have the numbers or limits, though.
Looking at the error message, you seem to be amassing an awful lot of calculations in one single field. My gut feeling is that this is very bad information architecture. What is the purpose of the form? What are you trying to achieve? Why would anyone have 60 fields in a form?
It looks as if you are summing a large number of cells. InfoPath is not a spreadsheet.
Use repeating tables to capture similar data. Then you can total the table entries with a standard IP function.
This looks like a sum of all the items a restaurant has on the menu. This is a perfect case for a repeating table. Don't use all 60 items on the menu in a list of 60 fields all in one form. That is overkill and not user-friendly. Create a repeating table structure where the user selects one of the 60 items and enters the transaction data. Each row of the repeating table can have another item of the list of 60. The grand total will be calculated from the entries.
If that is not viable, use helper fields to calculate sub totals by item category, and create a grand total from all the category totals.
Related
I want to calculate and display the average scroll depth in Data Studio from analytics.
I’m looking to get an average scroll depth in Studio. I’ve got the 10%,25%, etc scroll depth data coming in, but I now need to be able to calculate the average scroll % from this data.
To calculate the average scroll depth:
multiply the scrolled threshold by the number of events (10x500) + (20x400) + (30x475) +(40x300) + (50x200) + (60x100) +(70x75) +(80x60) + (90x20) + (100x10)
Then, take that total divided by the total number of events. 500 + 400 + 475... etc
Because I can’t reference cells in Studio I can’t get it to work. I’ve also tried Google Sheets, which does work to do the calculation, but then I can’t use Data Studios filter to provide a specific page path?
I'm thinking that perhaps the calculation will need to be done at data source, but I am not sure how to reference a 'cell'?
Data Studio doesn't work based on a concept of "cells", it works based on a concept of "fields"—which are basically properties of the data source. Similarly, you don't have "formulas" per se, but rather "calculated fields". These fields can be created either at the chart-level (single-use, but doesn't require permissions to modify the data source) or in the data source (reusable across many charts, requires permissions to modify the data source). Most fields also have an aggregation type, which tells the report how to aggregate it in charts by default (e.g. Sum or Average).
When you either edit your data source and hit "Add Field" or the option with the same name under the "Add metric" or "Add dimension" menus on a chart, you'll be presented with a box to input the formula. To access a field, just type its name (of if you're in the data source, select it from the list on the left). The editor will also typically give you an auto-complete list below your cursor based on what you're typing. Once your entry matches a field, it will get a highlight box around it (the color is based on the type; green = dimension/string,blue = metric/number). The functions available are sort of a mash-up of something between what you'd expect in Google Sheets and in a SQL query, but with more constraints on when you're allowed to use certain functions.
The documentation for calculated fields is pretty simple, so I'd recommend starting there before you try to do too much heavy-lifting in Data Studio. Because of constraints in Data Studio's data model, you'll often find that you need to create separate calculated fields for different parts of the formula, and then combine them in a new calculated field. I'll warn you that the error messages in the field editor aren't super helpful sometimes, so you may need to re-read the documentation for the functions and field types you're working with to ensure you get a valid result.
If you're running into problems, including the field names and values that you need in your calculation may help, including the source of the data (are these GA events?). The more details you give, including what you've already tried, the more helpful we can be. Also, make sure to read the docs first to make sure you have a good handle on the product you're using and the terminology the community is most likely to understand.
"I want to implement Gridview custom paging with full text search, with each individual page being bound to only 10 results/records.
My current setup fetches all the search results (rows) on each button click but displays just 10, making it very resource intensive. If it is of any consequence, in my current pagination setup I have first, next, last and previous buttons beside the actual page numbers.
I would like to retain the same scheme but only have it fetch up to 10 results for each page and display as many at any given time.
Should I work on adapting this particular method:http://www.c-sharpcorner.com/UploadFile/99bb20/custom-paging-with-gridview-control-in-Asp-Net-4-5?
If yes, do you have any suggestions as to how i could go about doing so in my case? If not, please suggest some alternatives?"
To fetch all the data while populating the grid for the first time is not a correct approach I think.
Depending on the page number and number of data that needs to be fetched, you need to get only that data from the database by sending the page number and page size qith your query.
So, when you click on First, Next, Previous and Last you send the page number and page size and get the data from database by calculating the total number of records.
Hope this provided you with an alternative approach.
Thanks!!
I am making a page in asp.net using C# and my page consists of two drop down list one for state and one for subjects, both the data are coming from database, and there is a third database table for storing user details and the third table consists of name class and subject
Now my problem is that on click of search button i want to search the users table and return the value selected by person searching through drop down list on the master page and the result will be displayed on the next page
Please help as to what to do for search button, and what to write on second page on which i want to display the results.
Your help is badly needed
Thanks in advance.
This sounds like a homework assignment... Have you tried to solve this already on your own? What did you try, and what-if-any problems did you run into?
Here's one (of a thousand other) tutorials that will walk you through filtering a result page using a drop-down.
http://msdn.microsoft.com/en-us/library/aa581789.aspx
Good luck!
I have created a small "Dynamic Data Web Site" using the Entity Framework. I've no experience with this really, but it looks very interesting. Anyway, I have a single table being displayed on a single web page. The table contains over 21000 rows and the page limits me to 10 records per page, which is all fine.
My problem is that the page is incredibly slow. I'm guessing that maybe every row in the table is being loaded whenever I try to navigate, but I can't be sure this is the cause.
How can I increase the performance of the page? I want to be able to click through pages of results quickly and easily. It currently takes more than 60 seconds to click to the next set of results.
this is usually caused by filters on a table where the filter has MANY rows you could fix this using the Autocomplete filter which prefilters the data base what the user types in.
You can get this filter and other from ny NuGet package Dynamic Data Custom Filters
Also try having a look in it using Ayende's EFProf. It is a commercial product but it has a free 30 day trial. I can sometimes point out silly things you are doing and suggest some ways to optimise your data access
I've got a situation where I want the user to enter a start date and end date for report data. In addition there should be a drop down which allows the user to choose one of the following:
last 7 days
last 14 days
last 30 days
If the user selects one of these values, the datepickers should adjust there values? I can't quite figure out how to approach this. Anyone have any ideas.
This isn't possible solely from within SSRS. However, you can still achieve your goal with a bit of extra work. Here's a bit of pseudocode to get you going. This technique works and we use it in our organization often.
In SSRS, hide the report parameters
Create a new blank HTML/ASPX page
Using only HTML, create create your own datapickers and custom "last 7 days" dropdown.
Use Javascript/jQuery on the client to handle your custom logic.
Place a "Generate Report" button on the page.
Insert a hidden iFrame on the page
When the user clicks "Generate Report", perform an HTTP POST passing the report parameters in the URL (something like http://server/reportserver?/dir/Report&rs:Command=Render&Parm1=VALUE1&Parm1=VALUE2&Parm1=VALUE3)
Display the report in the iFrame
Your users won't know the difference and this will give you total control over the layout and presentation of your report parameters.
You can do this within in SSRS. Not great but acceptable.
Have the first parameter be a pick list with two choices.
Pick Dates or Last X Days.
Have the next parameter be the start date.
The third parameter is another pick list. It is either a list of dates or a list of numbers depending on the choice they made in the beginning.
Another way would be to have two reports displayed to the user. one with an open date range and one with a predefined pick list of dates. These would be linked reports that call the same underlying report but display different parameters. This is the approach I would take for such a user request.