You are building an integration by using Dataverse. As part of a single request, the integration must create a new row if it does not already exist or update the existing row by using supported…

Question

Options

• AClient-side script
• BCloud flow
• CBusiness rule
• DPlug-in
• EPCF control

• A
  79% (26)
• C
  6% (2)
• D
  15% (5)

Explanation

Options A (Client-side script), B (Cloud flow), and E (PCF control) are correct because all three can directly invoke the Dataverse Web API's native upsert capability - using an HTTP PATCH request with an alternate key, or via built-in actions like Cloud flow's "Add a new row or update an existing row" - allowing a single request to conditionally create or update a row without prior existence checks.

D (Plug-in) is wrong because plug-ins are server-side event handlers that fire in response to Dataverse pipeline events (e.g., Create, Update); they are not integration mechanisms you use to initiate the request, and they do not expose the upsert pattern as an outbound integration channel.

C (Business rule) is wrong because business rules are declarative form-logic tools (show/hide fields, set values, validate input) and have no ability to perform CRUD operations or interact with the data layer programmatically.

Memory tip: Think "Who holds the pen?" - the three correct options (client script, cloud flow, PCF control) are the actors that actively write data to Dataverse via the API. Plug-ins and business rules are reactors that respond to what others write; they don't own the integration request.

No community discussion yet for this question.