You’re offline. This is a read only version of the page.
Hi all,
We face a strange behavior when using environment variables for a sharepoint related flow we are working on.
When defining a environment variable for a sharepoint list view (by defining i mean the view's GUID), it does not resolve to the corresponding view upon importing the solution to our production environment. It works fine in dev etc, but when exporting and importing the solution , it does not resolve, even if we provide the right view values from the target environment.
As a result, the flow is not turned on and cannot even turn it on manually if we dont edit it and reselect the right view this time.
Anyone with the same issue or a similar one?
Thanks in advance!
Its still a topic, it seems to be some kind of issue where all the columns dont appear, but if you are able to save and re open the flow they will appear again. The real problem is when you cant save then you gotta clear the action and reset it. It took my alot of fiddling to finally get environmental variables for views to function properly.
Is this still the same topic? For me it is a difference if the flow can't be turned on because the view is not found or the view is found but doesn't get all values (maybe because some columns don't have all fields filled out).
Is your problem fixed @Arvitis
OK, now I think I understand the topic. You need 3 Environment Variables in this case.
1.) Sharepoint -> Site (connected to the sharepoint)
2.) Sharepoint -> List (connected to variable 1 and to the list)
3.) Text -> GUID from the view
Works for me.
for the environmental variable I am using Text but that does not work. Also using variables of type string does not work either it was working at first then applying lower in the flow corrupted the flow. really annoying I am not sure what to do from here.
#1
Michael E. Gernaey
497
Super User 2025 Season 2
#2
David_MA
436
Super User 2025 Season 2
#3
Riyaz_riz11
244
Super User 2025 Season 2
Share
Report
All responses (
Answers (
