Please do not crash my workflow in the action "Remove user from a SharePoint Group".
It is absolutely wonderful that you return an object that tells me if the removal was successful or not. That is exactly how it should be for every action.
BUT (crying sounds in the background) still the workflow crashes if the user cannot be found! See screenshot.
Please please never let workflows fail for things like this. I am sure you're going to fix this... ;-)1 vote
When I add a member to a team in MS Teams and it cannot be added for whatever reason currently the workflow bluntly crashes.
Please don't do that to us ;-) That is sooo 2020.
Can you please return an object that tells me if it was successful or not?
This is not just the case for this MS Teams connector action but it still happens in more actions. Golden rule is to never ever crash a workflow for such a reason but always return a 'success' object. Thanks!1 vote
Would like to have ability to be able Preview and Print the NWC Form after Form submission.
[ ref:00D90q6Cb.5002v2r1FCN:ref ]48 votes
Thanks for the suggestion.
Just some clarifying questions – is the need to preview and print the form submission extending beyond the time of the initial submission. i.e. able to come back in x number of days and be able to view the form submission?
Would be great to have an option like in Power Automate where you can create secured inputs so that the collected data cannot be viewed from the instance start details.6 votes
Thank you for the suggestion.
Is this a matter of just protecting the view on the instance start details? or is there more to consider when classifying the secured inputs?
- Don't see your idea?