Configuring Product Release Dates via Lifecycle States
Short answer
C Configure the product lifecycle state to control whether the limited-edition bicycle is allowed on sales orders before its official release date.
Question
Where should you configure this?
Key Takeaways
The trap is confusing the UI location (Released Product page) with the functional control mechanism (Lifecycle State); the state enforces the business rule, while the product record just hosts it.
Learn how to use Product Lifecycle States in Dynamics 365 SCM to restrict product availability until an official release date, ensuring limited-edition items are blocked from sales orders.
Common mistake: Choosing 'Released product' because the configuration interface is found there, missing that the actual logic for blocking/unblocking based on time is driven by the assigned lifecycle state.
Expert Analysis
The question asks where to configure the "official release date" for a limited-edition bicycle, specifically referencing the requirement that it must not be allowed on sales orders until that date. This is a Product Information Management (PIM) scenario in Dynamics 365 Supply Chain Management.
Product lifecycle states are designed to control business processes based on the product's status. By assigning a lifecycle state (e.g., "On Hold" or "Pre-Launch") and configuring the system to block sales order inclusion for that state, you enforce the release date constraint. The comments correctly identify that lifecycle states provide this control mechanism. One comment notes that while the setting is applied via the Released Product page, the concept being configured is the lifecycle state itself. Another comment clarifies that lifecycle states can block products from sales orders, which is the core requirement.
The most attractive wrong answer is A (Released product). Users might choose this because the configuration UI is located within the Released Products list. However, the "Released Product" record holds static attributes; it does not inherently manage time-based process controls like release dates without the aid of lifecycle states. Option D (Default order settings) manages global defaults for orders, not product-specific release constraints. Option B (Sales price trade agreement) handles pricing, not availability timing. Therefore, C is the correct conceptual location for this control.
Official Reference
https://learn.microsoft.com/en-us/dynamics365/supply-chain/pim/product-lifecycle
This link opens the official vendor documentation in a new tab.
Exam Strategy
When asked about controlling business process eligibility (like sales order inclusion) based on product status, look for 'Lifecycle States' or 'Engineering Change Management' features rather than generic product records. Always distinguish between where you click (UI) and what feature provides the logic (Functionality).
Frequently Asked Questions
Where do I physically find the lifecycle state setting?
Can default order settings block a specific product?
Community Votes
100% of anonymous learners picked answer C. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 8 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 8
-
SDK_1234 👍 3It's a released product you couldn't meet all the requirements with just lifecycle states. The SO requirements ie max 1 is set on the default order settings. It correct as released product.
-
H_Incandenza 👍 2 Answered CI would have never known this because I don't have the license for Engineering Change MGMT turned on. See the below link: https://learn.microsoft.com/en-us/dynamics365/supply-chain/pim/product-lifecycle#enable-and-apply-detailed-control-of-business-processes Key phrase is, "It's possible set up your system to provide control over which business processes should be allowed or blocked by the system for a specific lifecycle state. This capability can be useful when introducing new products (where, for example, it may be possible to purchase the item but receive a warning that it's still a prototype) or to discontinue or end-of-life of a product (where it may be possible to sell the existing on-hand but not to purchase it or to produce it)." So lifecycle states work for this. But my guess is that many of us haven't seen this in use because until very recently it was an optional feature.
-
Gemami 👍 1 Answered CCorrect answer: C. Product lifecycle state Why C? Product lifecycle states can control whether a product is allowed on sales orders. Limited-edition bicycles can remain blocked until their official release date, then be made available for sale. Why not others? - A. Released product: Contains product settings but doesn't directly enforce release-date restrictions. - B. Sales price trade agreement: Controls pricing and validity dates, not whether an item can be ordered. - D. Default order settings: Controls order quantities, sites, warehouses, and related defaults, not product launch restrictions.
-
Max2969 👍 1A. "You can manually update the product lifecycle state by using: The Released products list page or Details view. The Released product variants list page or Details view. Find the obsolete products or product variants based on demand and associate a lifecycle state." https://learn.microsoft.com/en-us/dynamics365/supply-chain/pim/product-lifecycle
-
Backoffice 👍 1As the requirement for the release date is: "Limited edition must not be allowed for inclusion on sales orders until release date", I would set the "Stopped" flag in the Default order settings (for sales order). In my opinion the correct answer should be D.
Show 3 more comments
-
Elyse0814 👍 1It's all in the wording, it asks WHERE should you configure this. Product lifecycle state is correct, but it is configured in the released product details page.
-
Vnes80 👍 1The question is about the official released date, so lifecyle states is correct.
-
PrzemoK 👍 1 Answered CI would choose C
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.