-
The commands will continue to work in FormsViewer, I believe - I'll ask Patrick to confirm. They would stop working in preview. If you purchase qRules, then the DLL won't expire, and the commands will continue to work in preview (filler) and in the browser in FormsViewer.
-
Hi, Arthur - you could use the trial of qRules to add the commands to your form.
-
Yes, FormsViewer is compatible with SharePoint 2016. :)
-
If the issue is with their product, which it sounds like it is based on what support has said, there isn't really anything anyone else can do to help. :)
-
Unfortunately, you'll need to use CAML to update the list from the form - or possibly you could do this with SharePoint Workflow? Have you tried either of those options?
-
Hi, Arthur:
FormsViewer doesn't support custom code - but it does support a Qdabra InfoPath code library called qRules. So - you could replace your form code w/ qRules commands (which are activated via rules) - then when your form is published to FormsViewer, the functionality will continue to work. qRules does have ...
-
Oh wonderful, glad I could help. Basically, we add an XPath filter to the repeating group in our eval statement. :)
-
I'm sorry - I'm having a hard time understanding. :) Any chance you can attach your template to a reply, under the options tab? Sometimes that helps me understand better.
-
That is so weird - esp. since it reproduces in a new form. What operating system / IP version? If you look under File> Account > About InfoPath you can find the version. Screenshots can be attached under the Options tab in a reply. If you haven't already, maybe try running a repair on Office?
-
Your text box is bound to a field - so is your dropdown. In this case, the rule needs to go on the text box - add a formatting rule to hide it unless the value of the dropdown is what you want. I've attached a sample - save the file locally, right click and select Design. From there, you can see the rule on the textbox & you can preview ...