Describe Dynamics 365 Sales →hardMultiple ChoiceObjective-mapped

MB-910 Describe Dynamics 365 Sales Practice Question

Exhibit

Refer to the exhibit.

{
  "name": "Cross-sell Opportunity",
  "customerid": {
    "name": "Contoso Ltd"
  },
  "totalamount": 50000,
  "pricelevelid": {
    "name": "Standard Price List"
  },
  "productlineitems": [
    {
      "productid": {
        "productnumber": "PR-001"
      },
      "quantity": 10,
      "salespricelist": {
        "name": "Standard Price List"
      }
    },
    {
      "productid": {
        "productnumber": "PR-002"
      },
      "quantity": 5,
      "salespricelist": {
        "name": "Standard Price List"
      }
    }
  ]
}

A sales team is using the Dynamics 365 Sales API to create an opportunity. The JSON exhibit shows the payload they are sending. The request fails because the product line items are not being added. What is the most likely cause?

⚠ Common exam trap

It's easy for candidates to assume modern REST APIs always support inline creation of child records, but Microsoft deliberately restricts this for certain entities in Dynamics 365 to enforce business logic and validation order.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

The API does not support creating opportunity products inline with the opportunity; they must be created after the opportunity exists

The Dynamics 365 Sales API does not allow creating opportunity products (opportunity line items) inline within the same POST request that creates the opportunity. The opportunity must first exist with a valid ID, and then the line items must be added via separate POST requests to the `opportunityproducts` entity. This is a fundamental design constraint of the OData-based API for Dynamics 365, which enforces a parent-child creation order.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

✓
The API does not support creating opportunity products inline with the opportunity; they must be created after the opportunity exists
Why this is correct
Opportunity products are child records and require the opportunity ID to be created separately.
✗
The pricelevelid is specified at both opportunity and line item levels
Why it's wrong here
This is allowed and not the cause of failure.
✗
The totalamount field is inconsistent with the line items total
Why it's wrong here
While the total might be off, the API does not enforce this at creation, and it would not cause line items to fail to be added.
✗
The product numbers 'PR-001' and 'PR-002' do not exist in the system
Why it's wrong here
If the products did not exist, the error would be about invalid product IDs, not about line items not being added.

Go deeper

MB-910 Describe Dynamics 365 Sales Practice Question

Exhibit

Why each option matters

Option-by-option breakdown

Related to this question