Newbie Questions

Re: Totals based on drop down selection

punkn00dlez — Thu, 20 Nov 2008 14:18:41 GMT

Perfect. Thank you so much for being patient with me. I like InfoPath a lot now, I hope I can dabble around in it some more.

Re: Totals based on drop down selection

chandrakanth — Thu, 20 Nov 2008 13:26:43 GMT

Hi,

You can fix the issues by just opening the form in design mode and publishing it again .

Re: Totals based on drop down selection

punkn00dlez — Thu, 20 Nov 2008 13:08:55 GMT

I can't open your form, it's telling me to open it from the location in which it was published.

Re: Totals based on drop down selection

Hilary Stoupa — Wed, 19 Nov 2008 21:45:04 GMT

I am attaching the template after making some minor modifications:

For your grand total, I put in a default value that sums all the cost nodes
For your category, since you had no default value set, the first item (which is the one you were testing with) was never able to be 'selected'. In effect, category was always blank.

Take a look and see if this is closer to what you want.

Re: Totals based on drop down selection

punkn00dlez — Wed, 19 Nov 2008 21:21:14 GMT

The form I started out with was the built-in IP template and modified it from there since I never used it before. Either way, here's the gist of the form, formulas intact.

Re: Totals based on drop down selection

Hilary Stoupa — Wed, 19 Nov 2008 21:03:10 GMT

So, what is the formula in the expression box that is giving you errors? Can you copy and paste it in here? If you preview the form, and put an amount in the 'total' field, and add line items that have an amount in the 'cost' field (if you have no sum of costs, you'll see an error) do you still have an error? I guess I'm trying to understand what is different between your form and the sample I created....

Re: Totals based on drop down selection

punkn00dlez — Wed, 19 Nov 2008 18:39:12 GMT

Yeah, the total field on the form is bound to the total data source and it's default value was "subTotal-cashAdvance" but I just recently learned I didn't need that, so I got rid of it and set the default value to 0.00. I've even tried created a new field element named percent, inputting the function we're working with, and then binding the expression box that's showing the errors with the percent element, and that didn't work either.

Re: Totals based on drop down selection

Hilary Stoupa — Wed, 19 Nov 2008 18:06:06 GMT

I wouldn't think so. Just hide the expression box with the div calculation unless the total field has a value in it. The total field on your form is bound to the total field in the data source, correct? and that field has a default value?

Re: Totals based on drop down selection

punkn00dlez — Wed, 19 Nov 2008 17:31:19 GMT

Alright, so I downloaded the file and understand what you're getting at completely, however unlike your total field, my total field is automatically calculated. Do I need to turn my total field into a regular text box and have the submitter total up the information themselves?

Re: Totals based on drop down selection

Hilary Stoupa — Wed, 19 Nov 2008 15:36:51 GMT

I'm attaching a quick sample to better explain what I mean. Right click the link, Save As, open in design mode and preview. Put an amount in the Total field, and add some rows to the repeating table with a category of A (use a capital A, that is what I used in my sum formulas). If total is blank and you have amounts in the table, you'll get 'Infinity' in the expression box with the div function. If total is blank and you don't have amounts, you get NaN. If total is zero, you'll have an error too, since we can't divide by zero. I've conditionally hidden another expression box with the same formula, so that you can see how it would only display when there is an amount in total. Hope this helps!

Re: Totals based on drop down selection

punkn00dlez — Tue, 18 Nov 2008 21:28:02 GMT

It still shows the NaN or -1.#IND on the design view and still calcualtes everything to be equal to zero. The formula checker says there's no issues with my (by my I mean your) formula either. So technically there shouldn't be anything wrong.

Re: Totals based on drop down selection

Hilary Stoupa — Tue, 18 Nov 2008 20:59:39 GMT

Nah, you aren't a bother at all. Everyone has to learn, and really, none of this stuff is all that simple.

Let's see. There are ways to make a default value or an expression box value 'conditional' but they are a little complex. What about if you conditionally format the expression box so it only shows if cost is not 0 and total is not 0? That way you don't display the expression box when it might have an error because of total being 0 (a divide by 0 error) or it being blank....

Re: Totals based on drop down selection

punkn00dlez — Tue, 18 Nov 2008 20:46:20 GMT

I'm sorry to keep bugging you with simple stuff. Here's my XPath code: sum(/my:expenseReport/my:items/my:item/my:cost[../my:category = "86810"]) div /my:expenseReport/my:items/my:total. The field will only have a value once the submitter fills in a field named "cost". Once that's there, the code above should execute and provide me with a percentage of the grand total. I want to make a rule that'll run when cost is not equal to 0.00, but the only option I have under expression box properties is conditional formatting which won't get the job done.

Re: Totals based on drop down selection

Hilary Stoupa — Tue, 18 Nov 2008 20:29:37 GMT

What field are you dividing by? Does it have a value?

Re: Totals based on drop down selection

punkn00dlez — Tue, 18 Nov 2008 20:08:16 GMT

My error was generated because the way I tried it was completely and horribly wrong.

The code you just posted shoots back one of 2 errors depending on how the expression field properties are set. As a decimal, I get "-1.#IND" and as text I get "NaN". These are showing up in design view when I see this. The "-1.#IND" shows up when I switch to Form view until I tell it to calculate and both the NaN and the -1.#IND just calculate to zero no matter what. I've tried some research on it, but I don't really know what I'm looking for so it makes it a bit difficult. I think the "-1.#IND" has something to do with an indent maybe? As for the NaN, I found some posts on here, but none seem to be terribly relevant.