A manufacturer's buyer wants a summary of a purchase order whose lines are still waiting on receipt. The order is already open in Dynamics 365 Supply Chain Management. Which design fits?
Select an answer to reveal the explanation.
Short Explanation
The order is already on the screen in front of the buyer. You ask the supply-chain copilot on that record instead of mailing a spreadsheet to a side assistant. A copied file goes stale the next time a receipt is posted against the order.
Full Explanation
Dynamics 365 Supply Chain Management already holds the purchase order, and the supply-chain copilot summarizes records in the app, including lines that are still waiting on receipt. The buyer should ask in the context of the open order so the summary stays on the live record rather than on a copy. Exporting the order to a side spreadsheet and asking a separate assistant detaches the question from the record and will miss the next receipt posted against it. Training a foundation model on a one-time download freezes an old set of orders and ignores the lines that are waiting right now. Computer Use that copies the order onto a slide adds a screen path for data the app already has open, which is not a missing API. Exam caveat: the in-app summary describes the record the buyer has open. It does not replace the posting history on that record with a side file. Operational check: open a test order that still has lines waiting on receipt, ask the supply-chain copilot on that record, and confirm the reply refers to that order rather than to a spreadsheet export.