InfoPath Dev

 Euw yah, that is tough because field is repeating. What I'd do is add another attribute to the Field called "set" or something, then set up the controls using main data source. Then on Submit, set "set" 1 and have rules on that to set the individual fields. This is hard to explain, please see attached.

 Hmmmm. I don't understand. Can you attach a copy of your template under the Options tab in a reply?

Don't worry about the trial expiration (if that is the 30-day learning countdown you are referring to?) - you can always download another trial and re-inject, or email me via the forum, and I'll update your trial in your form, okay? qRules has a LOT of different features - maybe you can outline what you are trying to achieve and I can ...

The rule on the repeating section that hides where checkbox is not = true should be correct. Rule 2 which has the condition 1 = 1 should be hiding all rows, so you should delete that. Can you give me a hint as to what the math in Rule 1 is supposed to be doing? Then I should be able to help you with that formula - sorry, I just don't ...

Can you attach a copy of your form under the Options tab in a reply? Yes, of course it is possible to get the position of items even with an external data source and XPath filters.

Check your SharePoint logs for info for the correlation ID. It may just be a server configuration issue - but the log files should give you more to search on.

 I've asked a colleague of mine to review the document you mention so we can either update it or clarify it. But could you try this for your command and let's see if that gets you any further: SubmitToSharePointList /submit=ShPSubmit /dsname=AddAttachment Your mapping file includes the attachment field, so you ...

Can I see a copy of your form? You can attach it under the Options tab in a reply. It is way more likely that the instructions are the issue & you are not. :)

So- in your calculated value for the "position" field, you could add the XPath filter to only include items where the checkbox field is true.

The error on binding shouldn't be a problem unless your form has code - if you search on the error message, you'll find a blog post I wrote on this. Basically, it is an InfoPath bug - calc'd values should not be bound, but sometimes IP adds that to the view and it causes an issueIsn't your formula on the repeating ...