InfoPath Dev

I am fairly new to infopath and am running into a minor problem.

I work in HR and built a form that connects to a couple of sharepoint lists.  The form includes a repeating table.  In the repeating table, the user enters a job code in the first text box.  I want the form to populate other fields in the row (job title, pay range, etc).  I figured out how to use the current() function and do a relative reference and got the fields to populate as an expression.

Problem is that I want to use the pay rate in some other formulas, so I need it to populate it into a text box.  If I use the same xpath formula from the expression in the default field of the text box, nothing happens.  It doesn't flag an error, just returns a blank cell.  I also tried to set the text box using a rule on the job code box - same result, didn't work.

If I re-create the situation outside of a repeating table or repeating section, it works perfectly (using either the default value or rule method).  Any thoughts?  I am totally perplexed.

Thanks, Justin

Hi, Justin:

Was the expression box you were using also located in the repeating section? What does the formula that is working in the expression box look like?

The expression box was also in the repeating section.  (I also tried a repeating table with the same results.)

The xPath formula I'm using in the expression looks like this (works as intended):

xdXDocument:GetDOM("Company Jobs")/dfs:myFields/dfs:dataFields/dfs:Company_Jobs/@PayRate[../@JobCode = current()/my:JobCode]

The expression box is considered to be at the same level as the repeating node, I think, and the text box is bound to a field in the repeating group, so a slightly different xpath is needed:

xdXDocument:GetDOM("Company Jobs")/dfs:myFields/dfs:dataFields/dfs:Company_Jobs/@PayRate[../@JobCode = current()/../my:JobCode]

We have to move from the field we are at up to the repeating node, then back down to get the JobCode.

Still no luck - same results.

I also tried the same xpath you suggested (and a few slight variations) attached to a rule on JobCode that set the value of the PayRate field with no luck.

Any other ideas?