-
Hi,
DBXL does not support writing data to SharePoint lists. For this, we recommend using qRules.On Hilary's latest blog post, you'll find a link of links with documentation on this related to qRules v4.2.
Hope this helps!
-
We did a webinar recently on this, but it was meant for users of Qdabra's DBXL. Are you using DBXL or qRules?
The concept is generally the same. You need to perform a search based on (in this case anyway) the user who has opened the form. If there is a form in the library that "belongs" to the current user, then you can show them a ...
-
You can leverage the information returned by the Active
Directory web service to simulate InfoPath User Roles, which are disabled in
browser forms. This was presented as a Qdabra webinar and as DBXL training for licensed customer, and is now available as a step by step tutorial. Click DOWNLOAD above to obtain the PDF.
-
Sure, here's an attempt. Hope it helps.
-
That's a good point.
What about storing the version in the main DOM (my:CurrentVersion) and ALSO read in the version from the processing instructions on Form Load (my:FormLoadVersion) and then, if they don't match, run the rule to set the date?
Just an idea - not sure if it will work though! Good luck!
-
I'm just guessing... You can set the value of a field to use the version number formula above, then have a rule that sets a date field.
I don't know whether this is exactly what you want, but I'm attaching a sample form that you can look at in design mode.
Good luck!
-
You should add a condition, such that the requester name is only autopopulated once (for example, when it is blank). It sounds like your data connection and/or your rule are executing with every form load, which is what it causing the issue.
-
You can display the form's version number from the processing instructions by adding an expression box (calculated value) by using this formula:
substring-before(substring-after(/processing-instruction()[local-name(.) = "mso-infoPathSolution"], 'solutionVersion="'), '"')
Hope this helps!
-
Hi,
The error message means that the command name is incorrect. The command is FilterOwssvr, not ExternalOwssvr.
Here is the step by step document. Hope it helps!
http://www.infopathdev.com/files/folders/qrules/entry49214.aspx
-
Hi,You can't add code to SharePoint list forms. If you click on Customize form in a SharePoint list, the form will open in InfoPath's design mode, then go to the Form Options -> notice there is no option for Programming.
qRules cannot be added to a SharePoint list form because SharePoint List forms cannot have code.
Instead, create a ...