PL-400 · Question #428
A company has a new implementation that will use Dynamics 365 Field Service. A developer adds two custom tables to the solution in a development environment. The custom tables have lookup columns to F
The missing dependency error when importing a solution with lookups to Field Service tables indicates that the Field Service application and its components are not installed in the target environment.
Question
Options
- AAdd the Field Service tables to the solution.
- BExport the solution as unmanaged.
- CAdd the custom tables to the solution.
- DInstall the Field Service application in test.
Why each option
The missing dependency error when importing a solution with lookups to Field Service tables indicates that the Field Service application and its components are not installed in the target environment.
Field Service tables are core components of the Dynamics 365 Field Service application and are installed with the application itself, not manually added to a custom solution.
Exporting a solution as unmanaged does not address missing foundational dependencies in the target environment; it only changes the management type of the solution upon import.
The problem states the custom tables are already in the solution; the issue is with their dependencies on Field Service tables, not the custom tables themselves.
Concept tested: Dataverse solution dependencies on Dynamics 365 apps
Source: https://learn.microsoft.com/en-us/power-platform/admin/manage-power-platform-environments#manage-dynamics-365-apps
Community Discussion
No community discussion yet for this question.