A distribution company's pricing depends on real-time inventory levels stored in an external ERP system, not in Dataverse. The sales team wants reps to see a live discount calculation on the Opportunity form based on that ERP data. Which extension approach fits this requirement?
Select an answer to reveal the explanation.
Short Explanation
The key detail in this kind of situation is the word live — the number on the form has to reflect what is happening in another system right now, not what it looked like yesterday. A form rule can only work with what is already sitting inside the platform, so it has no way to reach out and ask an outside inventory system anything. A lead-scoring tool is built to judge how promising a prospect is, not to run a pricing calculation on a deal that is already in play, so pulling it in here just borrows the wrong kind of intelligence for the job. A nightly refresh gets close, but it always shows yesterday's picture, which breaks the live requirement the moment inventory shifts during the day. What actually closes the gap is putting a small embedded app directly on the form that reaches out to the external system through a connector and brings back a number that is accurate at the moment someone is looking at it.
Full Explanation
The correct answer is B. The requirement is for a live, calculated value shown directly on the Opportunity form that depends on data living outside Dataverse, in an external ERP system; an embedded canvas app can call a custom connector to that ERP system in real time and render the calculated discount right on the form, satisfying both the 'live' and 'on the form' parts of the scenario. Option A is incorrect because business rules operate only on data already present on the form or in related Dataverse records and have no mechanism to call an external system, so they cannot retrieve real-time ERP inventory levels. Option C is incorrect because the Sales Qualification Agent is designed to assess and score leads, not to calculate pricing or discounts on an active opportunity, so repurposing it for this task misapplies the tool. Option D is incorrect because a nightly batch update produces a discount based on the previous day's inventory, which fails the scenario's explicit requirement for a live, real-time calculation rather than a stale snapshot.