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.
I had the need to give our users a way, to register external users through the SharePoint interface for a custom solution also based on SharePoint.
It was a little bit tricky to get a token from Graph to use it in the next action.
To save your time, I document it here…
register an app on https://apps.dev.microsoft.com/
make sure, you grant the application appropriate permissions in Azure AD. In my case it was “User.ReadWriteAll” (application permission!)
then generate a password and also note down the application ID (you need it later);
in Azure AD grant the application the admin consent for the permissions!
In Flow add an action “HTTP Request”
Note that the body content must be URL encoded
Now you have to get the token out of the response;
use the action Initialize Variable and a custom expression (where ‘GetAccessToken’ is the name of the action from before!)
again use an action HTTP Request to do the POST
(1 votes, average: 5.00 out of 5)