-
Thanks - when you tested to see if there is an error, did you remove the rule action to close the form? Since the QdabraRules data source is a secondary data source, the error will only be present for that session.
-
Can I see your form? You can attach it under the Options tab in a reply.
-
Okay, I think I understand what you are saying. If the form has its code, the SubmitToSharePointList command fails (doesn't create the list items) and if it does NOT have the code, the SubmitToSharePointList command succeeds (DOES create the list items). Is that correct? If you look at the QdabraRules data source, you'll see there is an ...
-
I am not sure if you are going to be able to access your SQL data source from the browser with SharePoint Online. I think you'll need to have your data in an Azure DB for that....
-
Your questions are not unintelligent - we are all new at things at one point. :) So - your button rule should run when the button is clicked. If you put the field you are setting on the form, does it get set? At the very least, I'd expect it to say "L". Does it work when you preview the form?
-
Wouldn't the rule be on the drop down box? When a data source is first queried, rules won't run on its fields (they haven't "changed" - which is what fires a rule - InfoPath considers the loading of data not be a change to that data).
-
Any chance I could take a look at your form? You can attach it under the Options tab in a reply.
-
Yah, I've had similar issues in the past - usually for some reason the relative path isn't resolving correctly from a subsite. In the manifest, search for xsf2:connectoid to find the info on the UDCX files. I think the issue will likely be with the siteCollection or source attribute there.
-
So - to clarify, you are saying you have another form with code (qRules) published as a browser form, with SharePoint Web Part Connection parameters, in Office 365? Because to the best of my understanding, this is not allowed in the Sandbox, and browser forms with code must be in the Sandbox on Office 365 as they cannot be admin approved. May I ...
-
Yes - forms with code that are not admin approved go in the sandbox. Forms in the sandbox can't have SharePoint Web Part Connection parameters. See the attached screenshot.