A company develops a new Microsoft Dataverse plug-in that manages the Update message of an entity. The plug-in logic requires access to the record columns before the operation starts and must…

Question

Options

• AAdd the code to the plug-in to read the record from the InputParameters collection.
• BRegister a pre-image by using the Plug-in Registration Tool. Add the code to the plug-in to read
• CRegister a post-image by using the Plug-in Registration Tool. Add the code to the plug-in to read
• DAdd the code to the plug-in to query the data from Dataverse by using the API call based on the

• A
  14% (5)
• B
  77% (27)
• C
  6% (2)
• D
  3% (1)

Explanation

When a Dataverse plug-in needs to access the values of a record before an update operation is applied, a pre-image must be registered. A pre-image is a snapshot of the record's columns captured before the pipeline executes the message. It is registered using the Plug-in Registration Tool and becomes available in the plug-in's execution context via the PreEntityImages collection. This allows the plug-in to compare pre-update values to post-update values. Option A (InputParameters) only contains the columns being changed in the current update, not the full prior state. Option C (post-image) captures values after the operation, not before. Option D (querying Dataverse via API) could work but is inefficient and may return already-updated values if called post-operation; using a pre-image is the correct, idiomatic approach.

No community discussion yet for this question.