{"id":976,"date":"2014-10-01T15:53:06","date_gmt":"2014-10-01T10:23:06","guid":{"rendered":"https:\/\/www.inogic.com\/blog\/?p=976"},"modified":"2014-10-01T15:53:06","modified_gmt":"2014-10-01T10:23:06","slug":"using-preentityimage-and-postentityimage-in-workflows","status":"publish","type":"post","link":"https:\/\/www.inogic.com\/blog\/2014\/10\/using-preentityimage-and-postentityimage-in-workflows\/","title":{"rendered":"Using “PreEntityImage” and “PostEntityImage” in Workflows"},"content":{"rendered":"

As we all know that we can always read Pre image and Post image in the plug-in for various purpose. However, in workflow, we may sometimes want to read Pre Image for some purpose. Now we can also read Pre Images and Post Images in the workflow using Execution Context. It uses the same Plug-in Architecture and hence we can use it to read Pre Images and Post Images. However, this concept is not documented in the SDK so it might be unsupported.<\/p>\n

The purpose could be to read the previous values from the entity record. For e.g. We may require it for Rollup Calculations in the Update operations since we need to see what the previous value in the Entity Record was and according to it we can perform some action on the same. For instance there is a field named as \u201cNo. of contacts\u201d on the Account, which maintains the number of sub contacts associated with the account, so when we write a workflow on update of contact (Parent Account) field, we need to read the Pre Image to update Old Account record field and Post Image to update new account field.<\/p>\n

\n

To read pre entity image you can read it like below:
\nEntity<\/span> contractedProductPreImage = context.PreEntityImages[“PreBusinessEntity<\/span>“];
\nTo read Post Entity Image you can read it like below:
\nEntity<\/span> contractedProductPostImage = context.PreEntityImages[“PostBusinessEntity<\/span>“];<\/p>\n<\/div>\n

Here, names such as \u201cPreBusinessEntity<\/strong>\u201d and \u201cPostBusinessEntity<\/strong>\u201d are used to read the Pre and Post Images.<\/p>\n

At times, it may not required to read Post Image from context as we can read the updated entity record by retrieving its data from the organization service or from the Input Parameters. In order to get the Previous Entity Record Values, the only option to get it is to read it from the Pre Image.<\/p>\n

The availability of Pre Image and Post image also depends on the events. As we know, workflows can also works in Synchronous mode i.e. Real Time Workflow. Below is the table that tells us when we can read Pre Image and Post image during different events and in different scenarios:<\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Events<\/strong><\/td>\nPre-Image<\/strong><\/td>\nPost-Image<\/strong><\/td>\n<\/tr>\n
Background Workflow<\/strong><\/td>\n<\/tr>\n
Create<\/td>\nNO<\/td>\nYES<\/td>\n<\/tr>\n
Update<\/td>\nYES<\/td>\nYES<\/td>\n<\/tr>\n
Delete<\/td>\nYES<\/td>\nNO<\/td>\n<\/tr>\n
On-Demand<\/td>\nYES<\/td>\nNO<\/td>\n<\/tr>\n
<\/td>\n<\/td>\n<\/td>\n<\/tr>\n
Real-Time Workflow<\/strong><\/td>\n<\/td>\n<\/td>\n<\/tr>\n
Create-After<\/td>\nNO<\/td>\nYES<\/td>\n<\/tr>\n
Update-Before<\/td>\nYES<\/td>\nNO<\/td>\n<\/tr>\n
Update-After<\/td>\nYES<\/td>\nYES<\/td>\n<\/tr>\n
Delete-Before<\/td>\nYES<\/td>\nNO<\/td>\n<\/tr>\n
On-Demand<\/td>\nNO<\/td>\nNO<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Conclusion:<\/strong><\/p>\n

We can read the Pre and Post entity images in the workflow depending on Synchronous\/Asynchronous Workflow and its events.<\/p>\n","protected":false},"excerpt":{"rendered":"

As we all know that we can always read Pre image and Post image in the plug-in for various purpose. However, in workflow, we may sometimes want to read Pre Image for some purpose. Now we can also read Pre Images and Post Images in the workflow using Execution Context. It uses the same Plug-in\u2026 Read More: Using “PreEntityImage” and “PostEntityImage” in Workflows »<\/a><\/span><\/p>\n","protected":false},"author":13,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[19,21,22,24,67],"tags":[740,1336,1355,1358,1409,1841],"class_list":["post-976","post","type-post","status-publish","format-standard","hentry","category-dynamics-crm","category-dynamics-crm-2013","category-dynamics-crm-2015","category-dynamics-crm-2016","category-workflows","tag-entity","tag-post-image","tag-pre-image","tag-preimage-and-post-image","tag-read","tag-workflow"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t