Share
Report
2Hello,
We have the business need that we have to make an email when specific fields of an account are modified and the email must contain only the values of the fields that are changed and the value before and after change. The fields are changed in the background by an integration with an external application, which we can't alter.
As solution I thougt of making a Power Automate flow that would be triggered by any of those fields changing and that would get the values and create the email. The only problem is that in Power Automate I can't get the values before the change was made. A kind of pre-image behaviour that we could use in a plug-in scenario. But I'm not a coding expert so I rather would go for a none coding solution.
I came up with the next idea:
Create a synchronous workflow (the non Power Automate version of workflows ;-)), that will be triggered by change of the same field but on the 'before update' action. And let this workflow save the 'old' values in a custom field 'oldvalueofxxx'.
In the Power Automate flow I now will be able to get the old and new value and compare if it is changed and report it in the email.
But I still have thougts about this solution if it is really what I want.. it feels a bit 'non-elegant' and I'm asking myself if I'm overlooking possible issues.
In pro's and con's that I see:
Pro's:
- easy to make
- standard no-code functionallity
- processlogs for failures and easy retry possibillities
Con's:
- not elegant....
- additional storage needed
- ??
What do you think about this solution and has anyone another ideau of solving this?
(I have found another solution which uses Azure servicebus but that's a nogo area for us at the moment)
All responses (
Answers (
