-
Wonderful - glad you got it solved. :)
-
I've not ever seen anything like that before. Does it happen in all browsers? Can you have a SharePoint admin check the ULS logs? Is this just using the built in ribbon submit functionality?
-
I'd drag the entire data connection onto the form so you have controls bound to it, and add a button that runs the query. Open the form, click the button - what happens? Hopefully you get an error w/ a correlation ID - which you can then give your SharePoint Admins so that they can investigate the ULS logs. :)
-
The only way I know how to do this involves code - and we can't use code with list forms..... but maybe this will help you: https://www.ilikesharepoint.de/2018/03/infopath-using-parameters-from-url/
-
Ick. https://docs.microsoft.com/en-us/sharepoint/troubleshoot/sharing-and-permissions/picker-field-embedded-does-not-show-add-people has some suggestions - you may want to install something like Fiddler on the machine for the user experiencing the issue so you can try to get more info about what is happening when they try to pick a person.... ...
-
I'd guess if it is SQL, you could. But I'm not sure - you'd have to try it to see. Like I said, I'd guess that Flow (Power Automate) or Azure Logic Apps would be the best approach, because you can use a REST request for the trigger and a REST response - so my guess is that a browser InfoPath form may be able to access that and ...
-
I copied your Save button in the default view and added a rule to set the ID query field and execute the query. Again - I'm not 100% sure on this, just a guess - but worth a try. So - query fields in your main data source only show up in advanced view. For SharePoint list connections, you can only use equivalence - think of query fields as a ...
-
You would need to explicitly set the ID query field in the main data source to the current item's ID prior to running the query. Feel free to attach a copy of your form, under the Options tab, if you'd like a hand.
-
Put a button on the form. For the button's rules, select the option to switch views. See attached - save the file locally, right click and select design.
-
Just use regular action buttons that change the view? Maybe have a field in the schema to keep track of what view the user has switched to, and use that when you open it to determine which view to open if needed? I don't think I understand why you'd need to submit every time? A regular button can just switch views....