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.
A Common Data Service (CDS) environment has two custom entities named Building code and Work item. Building code has a code date custom field and Work item has an elapsed time custom field. Construction workers use a consolidated custom form with data from both entities to fill.in their daily work items.
A JavaScript library is used with these custom entities and fields to apply complex logic.
You need to ensure that the JavaScript library continues to function as originally designed if other developers expand the environment.
Solution: In the JavaScript library, add Building code with Code date and Work item with Elapsed time in the dependencies tab.
Does the solution meet the goal?
A . Yes
B . No
Answer: A
Explanation:
Within a solution you can define dependencies within solution components. Up until Dynamics 365 for Customer Engagement apps version 9.0 the main purpose of these dependencies was to prevent the deletion of a solution component when another solution component depended on it.
The following image shows the dependencies tab within the web resource form.
Dependencies between web resources are set in the top list.
Reference: https://docs.microsoft.com/en-us/dynamics365/customerengagement/on-premises/developer/web-resource-dependencies