Forum Discussion
Update the Sharepoint List Name with last update
jtsables it is possible using a flow in Power Automate but you will need to use environment variables in a solution so that you don't have to keep manually changing the source list name. My original SharePoint list was titled Bridge:
This is the flow and you'll see the site name and list name are using the environment variables I created in a solution:
We need to use 2 send an http request to SharePoint actions, the first to get the previous title of the list and the second to post the new title.
After an item in the list is created or modified this is the new title of the list:
And again a couple of minutes later.
Rob
Los Gallardos
Microsoft Power Automate Community Super User.
Principal Consultant, SharePoint and Power Platform WSP Global (and classic 1967 Morris Traveller driver)
jtsables it is possible using a flow in Power Automate but you will need to use environment variables in a solution so that you don't have to keep manually changing the source list name. My original SharePoint list was titled Bridge:
This is the flow and you'll see the site name and list name are using the environment variables I created in a solution:
We need to use 2 send an http request to SharePoint actions, the first to get the previous title of the list and the second to post the new title.
After an item in the list is created or modified this is the new title of the list:
And again a couple of minutes later.
Rob
Los Gallardos
Microsoft Power Automate Community Super User.
Principal Consultant, SharePoint and Power Platform WSP Global (and classic 1967 Morris Traveller driver)
Dear Rob_Elliott
I succeed to finalize the flow as you did with the old designer and without the 'for each' action
And everything works very well!Thank you very muchCan you please explain me why we had to create environment variables instead of directly take the sharepoint site as usual?Best regards
Jean-Tristan
jtsables in fact the environment variables was my mistake. I didn't think the list title in the trigger would update when the title was changed and so the flow would fail. But I've just tested it on a different flow and it does update. This indicates to me that the trigger and subsequent actions display the current title but actually use the internal GUID of the list. Even after 5 and a half years with Power Automate you can still learn something new every day! Sorry for giving you the extra work with the EVs and solution (although they are often a good idea and it's good to know how to create them).
Rob
Los Gallardos
Microsoft Power Automate Community Super User.
Principal Consultant, SharePoint and Power Platform WSP Global (and classic 1967 Morris Traveller driver)Thank you very much, I learnt a lot with this exercise !
I'm glad you learn also something with this discussion.
Best regards
Jean-Tristan
I just have issues with the first http request and a part of the Uri formula:
actions('Get_item')['inputs']['parameters']['table']Do you know where is the problem?jtsables literally just paste _api/web/lists(guid'@{actions('Get_item')['inputs']['parameters']['table']}')?$select=Title directly into the Uri field, it will create the expression.
And you don't want that get item inside a for each - one of the issues with the new designer, which was why my solution used classic.
Rob
Los Gallardos
Microsoft Power Automate Community Super User.
Principal Consultant, SharePoint and Power Platform WSP Global (and classic 1967 Morris Traveller driver)Yes this is what I did the first times but I always have this message:
I was wondering the 'for each' on my get item created this issue but I cannot figure out why
And I still have this problem with the old design
- Dear Rob,
Wahoo, this is impressive and exactly what I need !!
Can you please explain me what are the twos "[@]PP-SiteEV" you put in your trigger and in some part of the flow? This is the first time I see it.
Thank you very much
jt
