-
Right - we use not(expression) because we are checking that a specific node DOES NOT EXIST.
!= compares values.
Thanks for adding this info, it will help ease confusion for others. :)
-
Is there anyone that has an answer to this or some suggestion? I am desperate.
Thank in advance!
-
Just wanted to update this thread in case anyone is looking for a solution to this. Seems there is a bug in infopath for this filter. If you put in 'equals' it will work. It will only show what was already selected. But if you put in 'not equal' it will not work, it will still show items in the dropdown that were already ...
-
I don't know of a tutorial, I'm afraid. With repeating data in InfoPath, a rule outside of the repeating group will set all instances of the field - so in the rules where you query your data connection, you could add another rule to set a field in your secondary data connection to some value that it would not currently be (so the ...
-
Below is the first form I am using I want a hyperlink on DESCR field. If I Click on the field it has to show the all the values in that particular row in different format (In a separate form) I will use the same REST URL as data source for the two forms.
-
Thanks for reply.
Is there any link to see the procedure. I am little bit confused with this
Thanks,
-
Set the Park query field in your Work Orders list data connection to the selected park in the main DS and run the query. If you get an error about the list item threshold, in the list settings in SharePoint, see if you can an index to the Park column. I believe that will get you around the threshold warning.
-
Depends on your target form & what you are trying to pass in - like if you want to open the list form for an existing item, you should be able to do that. You just need to figure out what the URL will need to be and then set one of the fields in the secondary data source you are not currently using - I leverage fields I don't need (like ...
-
Yeah, I'm confused, sorry. Does your filter in your REST URL use lowercase and you need it to be upper case? I think there is a to upper in SharePoint REST. Maybe this will help you? http://docs.oasis-open.org/odata/odata/v4.0/errata02/os/complete/part2-url-conventions/odata-v4.0-errata02-os-part2-url-conventions-complete.html#_Toc406398124
-
yes filter is not finding lower case letters as my list data contains all in upper case