Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.
You are setting up assets for a customer.
The VP of Field Service wants to have greater visibility to all the serialized components of an asset in a hierarchical view.
Solution: You define the Top-Level Asset with as many parent-child sub-assets as necessary, rolling up for viewing in a hierarchy.
Does this meet the goal?
Answer(s): B
Explanation:
Use multi-level assets.
Instead use the solution: You create each serialized component as a sub-asset to its parent asset.
Multi-level assets
You can create assets and related sub-assets in a hierarchical tree structure. In this way, you can show relations and dependencies among assets. Maintenance jobs can be related to all levels of the tree structure. Statistics can also be created for an individual level or as a sum of all sub-asset levels.
On the All Assets list page (Asset management > Assets > All assets), the Asset column lists assets in hierarchical order. The Parent column shows the related parent. Additionally, if assets and sub-assets have already been created, the Asset tree section in the Related information pane shows the assets in a tree structure.
Reference:
https://learn.microsoft.com/en-us/dynamics365/supply-chain/asset-management/objects/multi-level-objects