Without going into the technical detail; the previous value made available in conditional start is actually the current value just before any updates are made to the item. When the item is updated, we lose the ability to get the value prior to the update.
To restate the workaround as indicated in the idea; create an additional column in the list or library and update this with the current value of the column of interest. Then when the actual column is updated, the previous value is still available in the additional column. Of course one need not make this additional column visible in the view or Form so the users are not confused.
An error occurred while saving the commentBart Evers commented
We would love this functionality as we need to send an email with specific changes of an item to people. And we don't want to send all the fields because they don't know what has changed nor we want to send an email on any change.
It is right there in conditional start after modified, when used in an action or even notification (send only changed fields), it would make lists more easy and we don't have to clone lots of columns (one for old , one for new value).Bart Evers supported this idea ·