General

Re: Lookup fields and Repeating Sections

AdamAustin — Thu, 05 Jul 2012 14:10:28 GMT

So I need to make all the repeating data come from one source, and the data that I only want one copy of come from a secondary source?

For example, someone enters a delivery note number and the total amount of items received. I only want one copy of each of these per submission of data, so I should use a secondary data source?

Re: Lookup fields and Repeating Sections

Hilary Stoupa — Thu, 05 Jul 2012 14:05:03 GMT

The data source is what's important - not the controls on the form so much. That is, it is the structure of the data source that determines the final data, does that make sense?

Re: Lookup fields and Repeating Sections

AdamAustin — Wed, 04 Jul 2012 07:35:16 GMT

Ah okay. I just assumed that would be the way to get the field to stop repeating every time a new item was created, as I only want one copy of Delivery Note Number and Total Number of Items Received in every submission of data.

Re: Lookup fields and Repeating Sections

Hilary Stoupa — Tue, 03 Jul 2012 21:55:10 GMT

Well, actually - the field is repeating. You've just bound it to a non-repeating control. That doesn't change the fact that in the schema it is in a repeating group, a sibling of the amount node. Every list item you create with this form will have a separate "Total received" field.

Re: Lookup fields and Repeating Sections

AdamAustin — Tue, 03 Jul 2012 21:38:14 GMT

Nope, just the one Total Received field. It's not in a repeating section. I've attached the .xsn if that's any help!

Re: Lookup fields and Repeating Sections

Hilary Stoupa — Tue, 03 Jul 2012 18:51:24 GMT

So, if there are multiple Amount fields - there will also be multiple Total Recieved fields? Do you need to be comparing the total of both?

Re: Lookup fields and Repeating Sections

AdamAustin — Tue, 03 Jul 2012 18:44:49 GMT

dfs:dataFields/my:SharePointListItem_RW/my:TotalRecieved != sum(xdMath:Nz(dfs:dataFields/my:SharePointListItem_RW/my:Amount))

Re: Lookup fields and Repeating Sections

Hilary Stoupa — Tue, 03 Jul 2012 17:42:23 GMT

Can you change the first dropdown of the condition to "The expression" and paste in the resulting XPath so I can see the whole condition?

Re: Lookup fields and Repeating Sections

AdamAustin — Tue, 03 Jul 2012 17:37:39 GMT

It makes total sense, but it doesn't seem to work.

I have a rule on the submit button so if Total Received is not equal to sum(amount), the Submit button is hidden. Here is the XPath of the sum(amount)

sum(dfs:dataFields/my:SharePointListItem_RW/my:Amount)

But it only seems to work in the first Amount field. It's not adding up all the Amounts from the repeating fields.

Re: Lookup fields and Repeating Sections

Hilary Stoupa — Tue, 03 Jul 2012 16:02:16 GMT

You are right - the point of a calculated field is to not have to add a field to the data source to display the results of a calculation.

However, you can use the same calculation for your conditional formatting. Add conditional formatting to your Submit button. For the first drop down in the condition, select the Total Number of Items Recieved field. Set the middle drop down to is equal to. For the third dropdown, use a formula - and you can use the same "sum" formula you are using in your expression. Make sense?

Re: Lookup fields and Repeating Sections

AdamAustin — Tue, 03 Jul 2012 15:43:38 GMT

That's fantastic, thanks!

On a tangentially related note, I now have a calculated field that adds up all of the values in the 'Amount' column. It works great, but i'd like to set it up so the Submit button is hidden unless the value in the calculated field is the same as the value in the 'Total Number of Items received' box.

I thought I could do this using conditional formatting, but the calculated field doesn't appear to exist in my list of fields...

Re: Lookup fields and Repeating Sections

Hilary Stoupa — Tue, 03 Jul 2012 15:32:50 GMT

So, this could be simplified:

xdXDocument:GetDOM("EP Parts List")/dfs:myFields/dfs:dataFields/d:SharePointListItem_RW/d:Part_x0020_Description[../d:ID = current()]

The current() function returns the current node - since you are in a repeating group, PartNo could have many instances. Your rule is on PartNo, thus current() refers this PartNo. :-)

Re: Lookup fields and Repeating Sections

AdamAustin — Tue, 03 Jul 2012 14:50:44 GMT

Hilary, I think I have fixed it... although I'm not quite sure how it works:

This is the XPath value now that it's working:

xdXDocument:GetDOM("EP Parts List")/dfs:myFields/dfs:dataFields/d:SharePointListItem_RW/d:Part_x0020_Description[../d:ID = xdXDocument:get-DOM()/dfs:myFields/dfs:dataFields/my:SharePointListItem_RW/my:PartNo_x002e_[. = current()]]

Re: Lookup fields and Repeating Sections

Hilary Stoupa — Tue, 03 Jul 2012 14:31:56 GMT

Hi - I think InfoPath may have "helped" with the filter (the bit in the square brackets in your actions) in an unhelpful way. Open the first rule, and open the formula editor (the fx button next to the value field). You'll find a checkbox that will display the full XPath - check that box. Then copy the result, and paste the formula here. I'm guessing that IP used a full XPath to PartNo_x002e_ instead of a relative XPath.

Lookup fields and Repeating Sections

AdamAustin — Mon, 02 Jul 2012 12:50:50 GMT

I have a form:

'Part no.' is a lookup field that has the following rules:

So basically it auto-updates Part Description, Serial Number and Size when a Part No. is selected.

The trouble i'm having is that when you insert a new repeating section and select a new Part No., the Part Description, Serial Number and Size fields in the new section get populated by whenever you chose in the very first section instead of by what you chose in the new section. How can I change this?