(myCol = the collection created in the ComboBox OnChange property)
First we check, if there are already values available in the source item
the OnChange makes sure, that whenever we select new items, the collection myCol will be updated accordingly
the Reset() makes sure, that the values in the origin dropdown will also be updated
the Clear() function resets the collection, when the user starts a new selection
the origin dropdown will always have the selected items from the ComboBox
last but not least, hide the origin dropdown and that’s it
One more important thing to mention! Keep the “Update” property of the datacard as “DataCardValuexx.SelectedItems” – if you try to pass in a table, the submit form function will fail. That’s the trick here.
Power App doesn’t provide functionality to just paste copied content from Excel into a table or a gallery. But it’s annoying people, if they have to type all the values from a calculated Excel file 1:1 into the Power App. So I found a workaround, that people can just copy & paste values from a standardized table, with which values they need to start an approval workflow for many times.
First we create a simple input form on Power App, containing a Text Input field, a table and a button. In my demo I use a SharePoint list as data source.
Then create a Flow with a Power App trigger.
Link the button to the Flow and pass in the text value.
Collection of formulas for you to copy:
Formula for the button:
Expression to get the rows: split(decodeUriComponent(replace(replace(uriComponent(variables(‘strRawTxtInput’)),’%09′,”),’%0A’,’#NEWLINE#’)),’#NEWLINE#’)
Expression to get the columns: split(decodeUriComponent(replace(uriComponent(items(‘ForEachRow’)),’%09′,’#TAB#’)),’#TAB#’)
When you create many workflow applications, you’ll learn, that most of them will use same data again like organization information, responsible persons etc. So I started setting up a “Central Data” location with all relevant info as SharPoint lists. Then I went to the different applications and created a “Get Centralized Data” Flow for each of them. BUT… trying to update a SharePoint People field, that has the setting “multiple selections allowed” turned out to be a pain. You can’t just use the dynamic value from the central list, even the fields were configured identically.
Put the person’s claims into an array variable, but don’t use “claims” but “Email” value (yes, it’s confusing ;-))
I created a Flow with trigger “SharePoint – When an item is created or modified” and went into an indefinite loop, because the system user modified the item and triggered the workflow again and so on. So I had to add a trigger condition, to not start if the “modified by” user is my system account.
It was a bit tricky to learn, that I can’t use “Modified by Email” – I had to use the editors vaule instead. Here we go…