Hi,
I've run into a bit of a snag. In a model-driven app the user can enter a folder name into a text field. A cloud flow kicks in when a record with this info is created or updated and creates the folder in SharePoint. After some head-scratching and experimentation, I've concluded that the SharePoint connector chokes on folder names with trailing (and perhaps leading?) blanks (strangely, I get a 502 Bad Gateway error after several attempts and an eventual timeout).
I could obviously trim the string I get from the record in the flow but that seems to be a shaky solution. I (or somebody else) may forget to do this in future flows so I'd like to fix the problem as far upstream as possible, preferably ensuring that leading/trailing blanks never end up in the field in the first place.
One thought I had was to have a separate flow triggered on Add/Change to just trim the field, but since the problematic flows already trigger on this I'm pretty sure I can't be sure the "trim" flow triggers before the "create folder" flows (yes, at this point I have two, one for Add and one for Change). Again, I could add the fix to the flows but that would pretty much land me with the same problem.
Can Business Rules somehow be leveraged here?
Any tips on how to achieve this greatly appreciated!