-
Im not sure how I missed that - thank you. All is working as expected I shall test further.
Just to reiterate my previous words - thank you for all your help on this its greatfully appreciated.
-
Doesn't the form open when you click "new" in the list?
-
Your screenshot doesn't show - can you attach it again under the options tab?
-
THank you so much. That is perfect!
-
You can use SetValue without a filter. If your button is outside the repeating group, just a regular rule would set all instances. If it is inside the section, you could use SetValue without an XPath filter to set all instances, or use a form logic field that sets all instances with a normal rule. :)
-
I know that I can use qRules SetValue to target a specific field in one instance of a repeating table, but how would I go about updating ALL instances of the same field in a repeating table? I am trying to hide all instances (sections) of the repeating table (ShowMtgInfo=false) and then target the specific row I am working on (using SetValue to ...
-
Tried this and a few other modifications. The logic makes sense, just not working the way we want it to. I am going to try a few more things. Thanks for the help
-
Scrap my last message Ive got the query list on form load working and so the form displays previously submitted entries on load - wooohooooo :)
All I need to do now is work out how I make the form available for people to fill in as when I launch the link after publishing all I get is a list view of whats been submitted not a ...
-
Thanks Hilary (I'm slowly understanding the process and how the forms interact with SharePoint lists).
A list is exactly what I want to achieve (which is now working when submitted which I tested from within InfoPaths preview function). How do I present the InfoPath form to the user to populate the list? Do I just upload the ...
-
This is normal behavior for a library form - which is why I had thought for this design you would want to use a list form set to manage multiple items.... I guess you could always only have one form in the library. Set the form name in the submit connection so it is hardcoded & set to overwrite.