InfoPath Dev

I totally agree! ^_^/~

Thank you for the follow up - interesting work around for the issue, but glad that quotes around the 2nd param of the substring function make it behave. :)

Thanks for the precision, I take good note. I tested again with my first variation, replacing the relative "." by "current()" as you have suggested and it is working # number(substring(local-name(current()), "2", 2)) gives # ...

Here's the template with my formula in place. I wonder if the issue you are experiencing is perhaps a difference due to the language on your OS?

My column names were changed when I created a list from your template - so the formula looks a bit like gibberish, but here is a screenshot of this formula working without an issue for me. I'll attach my copy of the template in another reply.

 To be clear - once your formula is referencing a secondary data source, the relative path of "." is now relative to the secondary data source. I've not seen InfoPath change punctuation in a formula before. I'll take a look at your files.

Hi Hilary, Thank you for the prompt reply. I did the test and it goes from # local-name(current()), 2, 2)) to # local-name(current()), 2. 2)) Please, be aware that the "." as a relative path is not the issue, it is the coma as a parameter separator in the function substring(,,) which change in a point to become the ...

 I think you just need to use current instead of "."? Did you try that?  xdXDocument:GetDOM("sp-list-connection")/dfs:myFields/dfs:dataFields/d:SharePointListItem_RW/d:list-column-requested[starts-with(../d:1st-column, "data-as-filter") and ../d:2d-column = number(substring(local-name(current()), 2. ...

Maybe they could also try updating their cached form? Open InfoPath Filler, under New, find the template, right click and select Get update or Remove?

I'm struggling a bit to understand what you are asking... Do you need to use a workflow for this, or will just a calculated column work? That is - is this new field also in the same library as the promoted data?