Form Builder - Columns and Calculations
Just a couple ideas...
Would love it would be nice if we had columns and the ability to span each field across columns, i.e. 1/3 and 2/3 or 1/3, 1/3 or 1/3. This would really cut down on the length of the form, imagine City. State, and Zip on one line.
If I did have columns, how great would it be to have fields that would do calculations. This would be a great feature for a budget.
Thank for your feedback around columns and formulas in application.
I would love a little more information:
1) do you need all of the data in table type question to be available in reporting OR would you want things like the total to be flagged and only those cartain fields be reportable?
2) what is the average size of these table 3×12 for examples?
Thanks for your thoughts as we considering implementing this into the solution.
Mike deHilster commented
I need this. We ask them to do math to calculate percentages, and I have to check every one of them. For example, we ask for Liability % of Net Assets and I have to have this instruction: "Divide 'Total Liabilities' field by the 'Net Assets End of Year' field. Enter as a percentage without percentage symbol. Please double check your math."
Zach Zarnow commented
It would be great if we could take two number fields or two currency fields and have them interact. For example, if an applicant says they want $10,000 in a request field and they will serve 100 people in a different field it would be nice to have a third field that would divide $10,000 by 100 and produce a cost per person calculation.
Gloria Dillard commented
Budget is what I would use it for. My budget worksheet consists of 13 columns and 54 rows. It would be nice to be able to access the budget worksheet in the reports so the grantees can report of actuals.
Budgets would be our main purpose, however, I could see myself using it for other purposes.
Our current budget table is 3 - 6 columns with roughly 10 - 15 rows.
For reporting I would need to export all the fields associated with the table, i.e. A1, A2, A3 or D3, D4, D5, with the subtotal of each column and then a combined total.
Thanks for considering.
Meg Hillmann commented
I feel that a feature like this would be useful for budgets (as previously stated by others) but also for establishing goals for outcome indicators.
1) Some of the grants we run are funded over 3+ years, so in the application phase we ask for each year of goals. In our prior applications, through a generic form builder, we were able to have the form auto-calculate and display the total for each goal for the life of the grant. Since these are the numbers the agencies will report against each year, they'd need to be able to be pulled into followups (progress reports) and the reporting function individually to measure projected vs. actual.
2) This might be a "prepare for the worst, hope for the best" answer, but I'd be inclined to think it'd be very rare to need a table over something like 10x50 and if you build it to support that, everything else would fit. That being said, looking back at our previous forms, I think the largest spread we had on a form was six non-totaling columns wide (http://prntscr.com/kfa89d).
Budgets would be our main use for this. Typically, we would want a table with 3-5 columns and 10-15 rows.
Sarah Winig commented
For us, we are looking to use this type of question for budget purposes. We are currently asking grant applicants to list their budget items in a separate Excel spreadsheet and then upload it into the application. We would love to have a table-type question where the applicant can enter things like the total materials being purchased by the grant. They would enter the item name, quantity, and cost for the item (3 columns) and the system would calculate the subtotal for that item and the total for all rows. I would guess the average number of rows would be 6 or less, but occasionally, there might be more. I think we'd just need the total to be reportable, as long as all data in the table was visible in the Application Packet. I'm happy to send you our Excel spreadsheet if you want a sample of what I'm talking about.
Thanks for considering the change!
Sarah Winig commented
We would also really like the ability to do calculations in fields. We ask our applicants to submit a budget and ideally, we'd like to setup a table with columns such as item name, number of each item, and cost per item. The applicant would fill out those fields and then a sub-total per item and a grand total for all items could be calculated.
We are also struggling with this feature at the follow-up point. The idea of adjusting the column or form to fit more questions on 1 row would be great. The idea of share questions certainly has good potential for generating follow-up from the LOI/application to the follow-up point. This means we can consider add more thought into building more into the application. But the main concern then comes at the point we build inline forms and obtain answers can the limited use of HTML be ideal here for citations, superscripts and all functionality that use more than your basic HTML? what are the work around in the current system?