LCS sandbox package deployment failed due to missing module dependencies

(2) Share

Report

Posted on by EK-26061005-0

437

Despite having the model parameters in the repository (in /Metadata/MyModel/Descriptor/MyModel.xml), the package deployment in sandbox environment has rolled-back due to the missing module dependencies. At this point i'm not sure if the issue is due to the pipeline build configuration or due to manually deploying AXDeployableRuntime in LCS.

Categories:

Dynamics 365 Finance

I have the same question (0)

All responses (9)

Answers (1)

André Arnaud de Cal... 299,024 Super User 2025 Season 2 on at

Like (1)

Report

LCS sandbox package deployment failed due to missing module dependencies

Hi,

Below there was already a comment that Tier2+ environments don't have all models. The FormAdaptor models don't exist on these environments, only on development environments. It looks like you just added all models as reference without actually using or extending the objects from these models. It is best practice to only include models from which you used or extended elements.

Was this reply helpful? Yes No
Verified answer

EK-26061005-0 437 on at

Like (0)

Report

LCS sandbox package deployment failed due to missing module dependencies

The problematic parameters were ApplicationPlatformFormAdaptor, ApplicationSuiteFormAdaptor, ApplicationFoundationFormAdaptor and FiscalBooksFormAdaptor. I have removed them via update model parameters and rebuilt the model. Looks like these modules were not used since the rebuild did not throw any errors. From this point the AXDeployableRuntime was installed on sandbox without any issues. Though i wonder why adding redundant parameters cause errors in LCS...

Was this reply helpful? Yes No
Suggested answer

Navneeth Nagrajan 2,179 Super User 2025 Season 2 on at

Like (0)

Report

LCS sandbox package deployment failed due to missing module dependencies

Hi EK-26061005-0,

A few suggestions:

1.The descriptor file of the core model have all the references compared to the package being deployed. The fastest way to check this is to download the package uploaded to LCS and check the repository as depicted below in the screen clip below. Also, run the build pipeline (pointing to the DEV Branch) and download the deployable package created from the build pipeline.

Compare the AxDeployableRuntime package extracted from the build pipeline (pointing to the DEV Branch) and the package manually deployed from LCS to the sandbox environment and there should a difference between the two. Compare the AOSService -> Packages and AOSService -> Files after extracting the AxDeployableRuntime.zip file. Compare the nupkg packages.

2. Check if the model is compiled in the build pipeline under the Build Solution step. If the model is not added then ensure you add a project and reference the project to the missing model. The section in red are the projects referenced to the model.

3. If it is an ISV model then ensure you add the ISV in the Copy Binary dependencies step. Sample YAML for reference.

Hope this helps. Happy to answer questions, if any.

Was this reply helpful? Yes No
EK-26061005-0 437 on at

Like (0)

Report

LCS sandbox package deployment failed due to missing module dependencies

Hello Nisarg Jani,

As you have said, the modules are also missing in the sandbox version's model list. How can i install them to sandbox and production? I thought these models were supposed to be installed along with the package as long as it's referenced in the descriptor file...

Was this reply helpful? Yes No
Suggested answer

Anthony Blake 2,711 Super User 2025 Season 2 on at

Like (1)

Report
LCS sandbox package deployment failed due to missing module dependencies

Hi @EK-26061005-0

Please could you share the referenced models in your descriptor here? Also the D365 version of your dev and sandbox environments?

I think there are a some possibilities here:

You have included some models in your references which are not deployed to a Tier 2+ sandbox. There are some models which only exist on Dev environments and are not intended for production use.

ISV dependencies, if you have any ISV models installed and referenced on your dev environment.

D365 versions, between versions some of the models are split out into multiple models in the core product. If you have a dev/sandbox version mismatch this is potentially your issue, and you need to align them and update your model references.

Thanks!

Anthony

Was this reply helpful? Yes No
Nisarg Jani 516 on at

Like (1)

Report

LCS sandbox package deployment failed due to missing module dependencies

Hi EK-26061005-0,

Can you check for the Model Descriptor Files that which models are been referenced in the File and check with the Sandbox that all the Models are there in the sandbox and Deployable Package?

To Check Models in the Sandbox you can check next to versions in the UAT / Sandbox Instance.

Regards,

Nisarg Jani

Was this reply helpful? Yes No
EK-26061005-0 437 on at

Like (0)

Report

Data entity extension custom fields are not in sandbox

Looks like i have missed the package deployment result in LCS as it has rollbacked due to the module missing a few dependencies. Weird thing is, the missing dependencies are available in the built repository's model descriptor file. I'll edit the post with relevant info...

Was this reply helpful? Yes No
Suggested answer

Mohamed Amine Mahmoudi 26,316 Super User 2025 Season 2 on at

Like (0)

Report

Data entity extension custom fields are not in sandbox

Hi @EK-26061005-0,

As Anton said, you need to refresh the entites in data management settings.

Best regards,

Mohamed Amine MAHMOUDI

Was this reply helpful? Yes No
Suggested answer

Anton Venter 20,291 Super User 2025 Season 2 on at

Like (0)

Report

Data entity extension custom fields are not in sandbox

Hi,

If the modifications were included in the build and deployed to the Sandbox environment, you can try to refresh the entity list.

Data management -> Framework parameters -> Entity settings -> Refresh entity list

Was this reply helpful? Yes No