Forum Discussion
Update list items manually in sharepoint using power automate
- Jun 04, 2020
rautchetan27 it's happening because by default Get items only returns the first 100 items. You need to go to the Settings (3 dots at the top right) for the Get items, turn on the pagination toggle and change it to something like 2000.
Rob
Los Gallardos
Microsoft Power Automate Community Super User
rautchetan27 you need to get the items from your list, then add an Apply to each and inside that apply to each add a Grant access to an item or a folder action. If you are removing access you could add a Stop sharing an item or folder action instead.
Rob
Los Gallardos
Microsoft Power Automate Community Super User
I want to user Filter query on Get Items, on the column of type users/groups
Users/Group Column DisplayName must match with one value in string variable.
how I can i do this comparision, because column which type is groups/users is not string so comparision is not working..
any idea?
- RobElliottJun 04, 2020Silver Contributor
rautchetan27 you can't use a Person/Group column in a Filter Query.
So you need to get all the items from the list and then add a condition that checks if the Vendor DisplayName contains the name of your Vendor.
If you want to do something with all the Vendors then you could do this with a Switch control based on the Vendor DisplayName and in each case you'd add the actions related to that Vendor.
Rob
Los Gallardos
Microsoft Power Automate Community Super User- rautchetan27Jun 04, 2020Brass Contributor
I am same logic and condition VendordisplayName contains, but getting following error
Unable to process template language expressions for action 'Condition' at line '1' and column '2851': 'The template language function 'contains' expects its first argument 'collection' to be a dictionary (object), an array or a string. The provided value is of type 'Null'.'.- RobElliottJun 04, 2020Silver Contributor
rautchetan27 you must make sure that the Vendor column always has a value in it and isn't empty (which is the reason for the error message).
Rob
Los Gallardos
Microsoft Power Automate Community Super User