I created a flow based on a trigger if an item was added or modified from a sharepoint list. I want to change this to just if one particular field is modified, but i don't know how to do that. Is the only way to rebuild the flow from scratch?
1. You can change the trigger by deleting the original trigger and then simply adding a different one. Complicating this procedure is the fact that you can't delete the trigger if any other components are using fields from it. So, if you had an email action that used fields from the trigger, you'd have to remove those fields from the email before getting rid of the trigger.
2. There is no trigger to start a flow from modifying a particular field of a list. The old way of doing this is to have an extra field to store the older value, and then compare them. For example, if your field is "status", create a new field called "status_old". The flow would fire for every list change, and would compare those values. If the values were different, then it should proceed on, doing whatever it needed to do, and then update status_old with the current value in status.
So basically, you would have to remove everything in the flow in order to remove the first trigger - essentially rebuilding it.
I've accidentally created a loop by having the trigger be create or modify an item at the end of my flow I have it update to Yes, if an item is approved - hence triggering another round of emails. I really need it to be if it is just changing one field. Doesn't sound like the old way would work for me anymore since the trigger is modifying a list. I guess I'll just turn off the flow to do a manual update for now. Thanks for your input!
in my case i had a long & complex workflow i din't want to recreate from scratch - especially since MS Flow kept complaining about dependencies between the trigger & actions that i could not find when i tried to remove the original trigger
so i found this workaround
in case you have a different datasource the edit may be more complex, just create 2 small workflows, one with each trigger, export them and look for the differences in their JSON files to help you in the right direction
that is a great idea, just got the problem, that i can not export a package ....
Actually i do not understand why as I am logged in with my Admin Account with an e3 License.
Is there an requirement for a special License?
Hi all, just opened a new question as i think it is appropriate.
This doesn't seem to work. When I change "When_a_file_is_created_or_modified_(properties_only)" to "When_a_file_is_created_(properties_only)" I get an unknown error on import.
this still works, just tested the change from "when item is created" to "when item is created or updated", no problem to import and use the edited version, there is also no reason that it would'n work as the JSON implementation is the same as two years ago
i have the same error when i forget to put the Microsoft.Flow at the root of the ZIP, so check that requirement
if you drop the exports (original and modified version) somewhere to download i can check what is wrong, be aware that some files may contain usernames so maybe remove them first
Another workaround can be this:
create a dummy condition like 1=1 and put all your code into this condition(works as a wrapper, I don't know a better way of making a wrapper for your code, there should be though), then copy it to the clipboard and paste it into a new flow that you created with the right trigger that you fancy. you need to fix the input of the actions that use the trigger output at the end, and tada!
an easier workaround is to copy the actions to clipboard and paste them into the new flow that you created with the right trigger. if there are many actions, I can suggest to create a wrapper to contain all your code, I normally do put everything into a always-true condition like 1=1, and this gives me more flexibility to move things around. I just copy the condition to clipboard and then can paste it in any other flow.
Check out the on demand sessions that are available now!
ISV Studio is designed to become the go-to Power Platform destination for ISV’s to monitor & manage published applications.
See the latest Power Automate innovations, updates, and demos from the Microsoft Business Applications Launch Event.