We have a flow that posts messages on Slack based on changed records from Salesforce
The condition is when a Salesforce opportunity record particular field called "stage" value is changed to "Closed won", the information is then processed by the flow to be posted on a particular Slack channel
The problem is that the same record will post on Slack multiple times afterwards, whenever it is changed (if the "stage" is equal to "Closed won")
Any idea how to avoid having the same records being posted more than once?
The two salesforce triggers available are "Record created" and "Records modified", and i understand that woulnd't be an issue if i am using "record created", but that wouldn't make sense because our sales cycle is quite lenghty and an opportunity might take months before getting closed won
I assume that you only want to post message on Slack channer when the value of a filed called “Stage” is changed to “Closed won”.
If yes, you may consider to add a Condition after the trigger “When a record is modified” to check if the value of the “Stage” field is equal to “Closed won”.
If yes, post the message to Slack, if no, do nothing.
Please try it on your side.
Please take this doc for a reference:
That is exactly how it is setup right now, please have a look at the attached screenshot
The problem is that the record will be modified afterwards (other fields such as amount or close date or opportunity details...), so from that point onwards, everytime the record is changed, it will post another message on Slack
The issue is that on the Flow conditions, there is nothing like "Changed to" instead of "Equa to"
We tried solving this by adding a hidden field on the opportunity object in salesforce (true/false) and update that field when the stage is changed to closed won, however Flow doesn't have an action to only update a certain field in Salesforce, you have to enter the values for over 50 fields, which is neither practical nor possible
Thanks for updating.
But I am afraid that currently there is no workaround can be used for the issue you are having now.
I believe that the idea adding “Change to” in the Condition would be a good addition for Flow.
Please consider to submit an idea at Flow ideas Forum:
I will help collect and report your request on my side.
The first Microsoft-sponsored Power Platform Conference is coming in September. 100+ speakers, 150+ sessions, and what's new and next for Power Platform.
Learn to digitize and optimize business processes and connect all your applications to share data in real time.
Are you new to designing flows? What is your biggest struggle with Power Automate Designer? Help us make it more user friendly!