InfoPath Dev

Hello,

I am hitting an awkward bug. As anyone ever seen it and is there a way to get around it ?

Thank you in advance!

I have a field named
# a01bc

I have a working formula for the default value of this field
# xdXDocument:GetDOM("sp-list-connection")/dfs:myFields/dfs:dataFields/d:SharePointListItem_RW/d:list-column-requested[starts-with(../d:cycle, "1st-filter") and ../d:q3j5 = 1]

I want to replace (end of the previous formula)
# ../d:q3j5 = 1
with
# ../d:q3j5 = number(substring(local-name(.), 2, 2))
where local-name(.) gives the name of the field, i.e. "a01bc"

Per itself
# number(substring(local-name(.), 2, 2))
is a working formula and returns 1 as expected

Now if I put it in the main formula, what happens is this
# 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(.), 2, 2))]
>> Error, Value type expected - Real Value: Number "[...] 2. -->2

So I played with the Modify an Xpath Expression CheckBox to have a better understanding
(1) box checked, copy-paste
# 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(.), 2, 2))]
>> 2, 2
(2) box unchecked
# list-column-requested[starts-with(1st-column; "data-as-filter") and 2d-column = number(substring(local-name(.); 2; 2))]
>> 2; 2
(2) box checked again
# 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(.), 2. 2))]
>> 2. 2

Seeing this I tried different things, none are working
- I tried to do it manually through infopath modal windows, error persists
- I tried formula variations, all working in standalone but not int the main formula
-- number(substring(local-name(.), "2", 2))
-- number(substring(local-name(.), number("2"), 2))
Those two variations allow the coma to stay a coma ( , > ; > , isntead of , > ; > . ) but no result is displayed nonetheless (verifiying the formula says it is fine in both cases)

Why no output ? Is there a way to go around it ?

Restrictions: IP 2013 w/ SP 2016 - Web form - no code allowed

Any idea or advice ?

Thanks in advance,

Jean-Christophe

 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. 2))] 

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 erroneous function substring(,.)

The second coma (,,) of the substring function is changing into a point (,.) when inserted in a request.

Really odd.

If someone can reproduce the behavior, it would be nice.

Files in the zip attached
- List template for SP
see PNG picture or you can use the manifest.xml and change "http://sp-dev/site_dev" by your SP site and convert the xml file in a .cab then a .stp (*)
- xsn w/o connection (one has to add it once the local SP list is created)
(*) https://chayadigital.wordpress.com/2011/08/05/manually-edit-a-stp-manifest-template-file-for-sharepoint/

 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.

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.

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?

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
# 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", 2))]
and is a working formula

Note that I have to put the first parameter of the substring function between quotes and infopath stops changing the following coma into a point.

So There is a bug and there is a way around.

Thanks again Hilary for the hint, I did not saw that one. Much appreciated.

(was writing while you were testing ;) just seen your last post, double checking is always good - thanks a lot)

I have InfoPath in Both languages and it did occur in each (but I realized that the manifest maintain the language whith which the form is created - did change it for you yesterday)
Clearly a bug in the parser and related to language management.

In conclusion:


For those whom are using a non-english infopath software use my variation
# number(substring(local-name(current()), "2", 2))

else use Hilary's solution
# number(substring(local-name(current()), 2, 2))

Thanks again!

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. :)

I totally agree! ^_^/~