InfoPath Dev

I think this would be the right formula: ../following-sibling::my:group2[my:Track = "true"]/my:CurrentRecord

My guess is your XPath of ../ID is incorrect. Right click the node in the datasource task pane and select Copy XPath - what is the path to ID? I'm guessing it may "d:ID" so you'd need ../d:ID instead.

Well - in my view, I'm still using the exact same field you were setting with the button! So you shouldn't have to change the promoted properties at all - my option buttons are leveraging the exact same field you were using already. :)

Here is a copy of your form w/ some minor edits - I added a new view to show you the approach I would probably take, with submit status set to Pending by default and some radio buttons that the manager can use to change it to Approved or Deny. Save the template locally (don't overwrite the one you are working on, of course) and then right ...

Oooh, just realized something else too - in your submit rules you set the status to Pending - so isn't that getting reset every time they actually submit? It gets set to Approve, then when they click the Submit button it goes back to Pending? And you have a rule on the SubmitStatus field that resubmits the form - that may be the submit you ...

Okay - so for your Submit button - that button is set as "Submit", not "Rules and Custom Code" - so it runs the rules you have in the Form Submit rules - which are all those rules that send the form to the right department library. Oh - I just noticed your warning at the bottom of the form - Honestly, I'd just copy those ...

Hi - I don't what "loses its concat formatting" means - but I'd be happy to take a look at your rules & see if I can see what's happening. You can attach your form to the Options tab in a reply.

Can you add an index to the list? Then don't query this list on load in your form, but instead use the query fields to get back only the data you need - set the query fields that determine which data you want and then run the query from a rule.

Well, I'd guess the schema is an issue here - I'm thinking you'd need two fields instead of one. One to bind the checkbox to, and one for the initial objectives. Is this form currently in use? If not, you could change the schema to use a repeating group with one field for the user to enter the objectives and another that was True / ...

Yuck, what a pain. Honestly, this is one of those cases I'd save the form as source files, open manifest.xsf with a text editor and search for the field that is getting set. The ruleset will have an identifier - usually you can search for that and find the field w/ the rule - but if it is on a button it can be trickier (if your buttons are ...