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 had the requirement to have a list input form in SharePoint online, that contains “Scope”, “Category” and a “Subcategory”. Of course – to have it end user friendly – these dropdowns had to be cascading.
First of all: as of today, cascading dropdowns in PowerApps only works smooth with TEXT only values!! (yes, it’s a real mess) So how to prevent the user from typing mistakes with text only fields? –> Provide the user a lookup input interface and create the text only values with a simple Flow.
First of all create the lists – 3 simple lists with Title only for the lookup values and 2 lists for mapping
In the mapping lists make the Title not required, add 2 lookup columns that are required and 2 additional columns for the text value
Create a simple Flow for each of the two mapping lists, that updates the text columns, that we’ll use later for our dropdown values
Then create a target list (also text only fields for these three “dropdown” columns!) Of course all other columns can be treated as standard.
In the main list click on “Customize Form” under PowerApps menu
Unlock the 3 Data Cards under “Advanced”, replace the text input controls with dropdown controls and rename them to something meaningful like “ddScope”, “ddCategory” and “ddSubCategory”
set the “UPDATE” property of the data cards to the name of the SP field to be updated with the value
Now modify the “Items” property of the new dropdown fields.
(if you want to sort the values, you can put a SortByColumns() function around the filter formula)
Now the lookups are already working, but if you click on Save, the values are not written to SharePoint. To fix this, we have to re-add the original columns to the form. When added again, unlock them under Advanced and set the “Default” property to the value of the dropdowns.