These column types contain a whole object, much more information than you need.Īnd as such they’ll need an extra expression to process them. I say ‘readable’ because you’re still dealing with complex SharePoint columns, e.g. The last step is to fill the array variable in a readable way. Place these expressions in their own ‘Compose’ actions for later processing. For the value in the previous version history, the output from the HTTP request: outputs('Send_an_HTTP_request_to_SharePoint')?Īnd for the value in the current item: triggerOutputs()? Navigating through the version history JSON, you can then take only the value for this specific column. In each loop it’ll take one of the modified columns and store it as the ‘Current item’ (=item() expression). Then add the ‘Apply to each’ to loop through the modified columns, the output from ‘Select’. As the first step, initialize an array variable, e.g. If you loop through that array, you can extract from the previous version only their values. The output of the previous post was an array with the modified columns – the columns you’re interested in. But you’re interested only in values of the modified columns, not all of them. Once you have the previous item, you can extract the column values and store them in a variable. output of this HTTP request will be a JSON with the previous version of the item, including all previous column values. Knowing this you can build the whole HTTP request, e.g. outputs('Get_changes_for_an_item_or_a_file_(properties_only)')? It’s one of the outputs from the ‘Get changes…’ action. The actual VersionId, which is required for the HTTP request, is a much higher number.īut that’s not a problem as the right number should be already available among your dynamic contents. You might be tempted to use the previous version number in the same way you did in the ‘Get changes…’ action. Note: everything inside are placeholders which you must replace. _api/web/lists/getByTitle('')/items()/Versions() If there’s an existing previous version, use a HTTP request to SharePoint to get it. That’s one of the reasons you need the version history, without it there’d be nothing to get. To get the previous field values, you must get the whole previous version of the item. Note: the version history on the SharePoint list must be enabled. But this one will include only the updated columns and skip the rest. The result of this post is an email similar to the alert sent on item update. And by values I mean not only the new value, but also the previous value. While it’s nice to know that a column was updated, it’s better to know also the actual values. Only the column internal names, nothing else. The outcome of that flow is an array with the changed columns. This post is an extension to the previous post ‘ Identify which SharePoint item columns were updated‘. “ Can I use Power Automate to send an email with the previous and new value in a SharePoint column? I’m interested only in the changed columns.”
0 kommentar(er)
