![\"Track](\"https:\/\/www.inogic.com\/blog\/wp-content\/uploads\/2021\/03\/1-tracking-specific-column-updates-to-SharePoint-List-Items.jpeg\"){kind=tracking}
<\/a><\/p>\nUsing the Column filter, we could provide the list of fields\/columns that if modified should the flow execute further. If none of the specified fields in the column filter were modified when this trigger was invoked, it would not execute the flow.<\/p>\n
This is really helpful when we would like to perform an operation only if that field was updated. Say, send an email notification when a ticket is assigned to a user. We need to identify if the update was triggered because of the change in user and only then send out the email notification.<\/p>\n
Similarly, when using SharePoint Lists as a data source, had a similar request. It was therefore required to identify if the user column had been modified in the item when the update was invoked.<\/p>\n
There is an existing flow template available to do this.<\/p>\n
However, this one too has the step to identify if the user field was modified missing.<\/p>\n When you add the SharePoint trigger;<\/p>\n We do not see a column filter where we can provide the list of columns that we are tracking.<\/p>\n To do the same in SharePoint, we need to perform the following action:<\/p>\n And set the following properties:<\/p>\n Set the SharePoint Site and List and provide the list item id for which the changes need to be tracked.<\/p>\n Since \u2013 should be set to the version # since when you would like to compare for changes. You could either enter a date or a version #. If you want to compare it with the original record the first time it was created set it to 1. If you would like to check for the columns that changed in this update since the last update, you need to set it to the last version # of the record.<\/p>\n Luckily for us, we get the version # of the current update in the trigger body.<\/p>\n Note: VersionNumber is not made available as a Dynamic value that we can use as it is, therefore to get the previous version number we can set Since to the following expression –<\/p>\n sub(int(triggerOutputs()?[‘body\/{VersionNumber}’]),1)<\/p>\n Ref: Sub function<\/a><\/p>\n With this included, the result of this action can now be referenced in the following steps:<\/p>\n Note: For Version # to be returned, you should first enable versioning on your SharePoint List.<\/p>\n 1) Navigate to your list -> Choose the Settings gear icon at the top -> choose List Settings.<\/p>\n 2) Here choose Versioning settings.<\/p>\n 3) Set Item Version History to true.<\/p>\n With this in place, though it requires a couple of additional steps, but we are able to implement the same feature as in the CDS (CE) connector and make sure to avoid unnecessary flow step executions.<\/p>\n Note: The flow would be triggered, i.e. it would count towards flow run even if the user was not modified or set.<\/p>\n Now if you wanted to make sure that the item has a value set for the user in the first place \u2013 since we need to send an email to the user, so we need to track the user’s data and it was changed since the last update.<\/p>\n The change since the last update or column filter was implemented above.<\/p>\n To incorporate the Row\/Record level filter, make use of the Trigger Condition available in the settings of the trigger.<\/p>\n Note: With Trigger Conditions added, if the trigger condition does not evaluate to True, the flow will not even trigger i.e. it won\u2019t even count towards your flow runs.<\/p>\n Hope this helps with tracking specific column updates to SharePoint List Items.<\/p>\n Attach2Dynamics<\/a> – Store and manage documents\/attachments in cloud storage of your choice – SharePoint, Dropbox or Azure Blob Storage from within Dynamics 365 CRM.<\/strong><\/em> Coming from a Dynamics CRM\/ Dataverse background and having written plugins and later flows using Common Data Service (Current Environment) connector, I was a little lost looking at the SharePoint trigger for When a list item is added or modified. With the CDS (CE) connector, when you use the When an item is created, updated,\u2026 Read More »<\/a><\/span><\/p>\n","protected":false},"author":13,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[16,19,1985,53],"tags":[2590,301,2171,592,1975,2183,2182,2589,2184],"class_list":["post-27089","post","type-post","status-publish","format-standard","hentry","category-dynamics-365","category-dynamics-crm","category-power-automate","category-sharepoint","tag-canvas-apps-more","tag-common-data-service","tag-dataverse","tag-dynamics-crm","tag-power-automate","tag-power-automate-cloud-flows","tag-sharepoint-list-item","tag-top-blogs-of-2021-power-apps","tag-track-specific-column-update"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/27089","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/users\/13"}],"replies":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/comments?post=27089"}],"version-history":[{"count":0,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/27089\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/media?parent=27089"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/categories?post=27089"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/tags?post=27089"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n
\nSharePoint Security Sync<\/a><\/strong> \u2013 Robust and secure solution to integrate Dynamics 365 CRM and SharePoint Security Sync thereby ensuring secure access to confidential documents stored in SharePoint.<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"