Develop integrations

A developer defines a new alternate key on the Account table combining two columns to support an integration that uses UpsertRequest with that key. Immediately after saving the key definition in the maker portal, the integration begins sending upsert calls, but they fail with an error indicating the alternate key is not usable. What is the most likely cause?

Your Dataverse environment generates thousands of account update events per minute that must be streamed to a downstream analytics platform capable of ingesting large volumes of data with consumer groups for parallel processing. You use the Plug-in Registration Tool to register a service endpoint. Which endpoint contract type should you select to best match this high-throughput streaming requirement?

You are building a nightly integration that copies only the records that changed in the Dataverse 'account' table since the previous run into an external reporting database. You want the Dataverse Web API to return both created/updated records and information about deleted records without you having to manually compare snapshots. What must you do first to enable this approach?

You are building a nightly console application that synchronizes Account records from Dataverse to an external reporting database. Change tracking is enabled on the Account table. On the very first run, your code calls RetrieveEntityChangesRequest without supplying a DataVersion (delta token). What happens, and what should your code do to prepare for future incremental runs?

You are building a nightly integration that copies newly created and modified Account records from Dataverse into an external reporting database. The Account table contains several million rows, and a full extract each night is too slow and consumes excessive API capacity. You want each run to retrieve only the records that changed since the previous run, including deletions, with minimal custom code. Which Dataverse capability should you use?

You are building a nightly synchronization process that copies new and updated Account records from Dataverse to an external reporting database. Change tracking is enabled on the Account table. On the first run you must retrieve all records and store a marker so that subsequent runs return only the records that changed since the previous run. Which Dataverse Web API request technique correctly retrieves the incremental changes on later runs?

You are registering a service endpoint with the Plug-in Registration Tool to stream Dataverse account creation and update events to Azure for downstream analytics. The consuming system must process a very high volume of events, replay events from a past point in time if the analytics pipeline fails, and support multiple independent consumer groups reading the same stream. Which destination type should you register?

You are developing a synchronous plug-in that must post a message to an Azure Service Bus queue registered as a service endpoint in Dataverse. The plug-in should hand the execution context to the registered endpoint at runtime so downstream Azure workloads can process it. Which approach correctly posts the message from within the plug-in code?

You are registering an Azure Service Bus service endpoint using the Plug-in Registration Tool to publish Dataverse Account events to a downstream integration. Testing reveals that some messages containing large custom entity payloads fail to post while smaller ones succeed. The team confirms the Service Bus queue and credentials are correct. Which explanation and remediation should you present?

You are registering an Azure Service Bus service endpoint in the Plug-in Registration Tool to publish Dataverse events to a queue. The downstream Azure Function that reads the queue is written to deserialize the message body directly as JSON without any additional decoding step. Which message format must you configure on the service endpoint so the receiving code works without extra processing?

Your company needs Dataverse to post the payload of every updated Account record to an Azure Service Bus queue so a downstream ERP system can process the changes asynchronously. You must register the integration using the Plug-in Registration Tool. Which sequence of registration steps correctly wires up this asynchronous message delivery?

You are building an integration that pushes product records from an external ERP system into Dataverse. The ERP sends its own unique product code (SKU) with each message, but does not know the Dataverse GUID. Records may already exist from previous runs or may be brand new. You must ensure each incoming message either updates the matching Dataverse record or creates it if none exists, without issuing a separate query to find the record first. What should you implement?

You are building a nightly integration that pushes product records from an external ERP into Dataverse using UpsertRequest with an alternate key defined on the 'productcode' column (a string field). During testing, some upserts fail with an error indicating the record could not be resolved, while others succeed. Investigation shows the failing ERP records contain product codes with leading or trailing spaces that do not exactly match the values stored in Dataverse. What is the most appropriate way to make the upsert reliably match existing records?

You are building a nightly integration that imports product records from an external ERP system into Dataverse. Each ERP product is uniquely identified by the combination of a warehouse code and a SKU number, neither of which alone is unique in Dataverse. The integration must create new products or update existing ones without generating duplicates, and it never has the Dataverse primary key (GUID). What must you configure to make UpsertRequest work correctly in this scenario?

You are building a nightly integration that pushes product records from an external ERP into Dataverse. The ERP does not store Dataverse GUIDs, but each product has a unique ERP SKU code. You have created an alternate key named 'erp_sku' on the product table. You need to write code that inserts new products and updates existing ones in a single operation per record, without first querying to check whether the record exists. Which approach should you use?

You are building a nightly integration that imports supplier records from an external ERP system into a custom Dataverse table. Each supplier has a unique ERP identifier stored in an alternate key column named 'erp_supplierid'. To avoid creating duplicates when a supplier already exists, you send an UpsertRequest referencing the alternate key. During testing, you need to confirm how the operation behaves and how your code can determine what actually happened. Which statement correctly describes the behavior of UpsertRequest in this scenario?

You are registering a webhook service endpoint using the Plug-in Registration Tool so that Dataverse notifies an external ASP.NET Core API when account records are created. The external API requires that every incoming request include a static shared secret in a custom HTTP header named 'x-functions-key'. In the Plug-in Registration Tool, which authentication configuration should you select to satisfy this requirement?

You are registering a Dataverse service endpoint that must notify an external ASP.NET Core API hosted at a public HTTPS URL. The endpoint must be invoked synchronously so the API's HTTP response can influence the outcome of the transaction, and the payload authentication should use a query string key. Which service endpoint type should you register in the Plug-in Registration Tool?

You are designing an integration where a Dataverse plug-in must call an external validation service during the record creation transaction. The plug-in registers a step against the Create message on a service endpoint. The external service must return a response that the plug-in evaluates before allowing the record to be committed. Which service endpoint type must you register in the Plug-in Registration Tool to support this requirement?