What is All-in-one deployable packages in D365 F&O

(0) Share

Report

Posted on by Rhushikesh R

758

Hi Everyone,

Can anybody please clarify me the concept of "All-in-one deployable packages" in D365 F&O?

I read the information from below link

https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/dev-tools/aio-deployable-packages

What I understood is its related to deployment package where you have more than one customized packages.

So my question is-

1. Do I always need to create a single deployable package of all customized model while deploying to Sandbox and Production environment?

2. Consider I have custom model A, custom model B and custom model C which have cross-references, which have already been deployed with some customization on Sandbox and Production.

Now I make some changes in model A and I create deployable package of only Model A and then deploy it to Sandbox, then am I going to lose all data of Model B and Model C?

As I found this kind of description on above mentioned link. Please refer below screenshot.

Need your thoughts on this concept.

Thank you in advance.

I have the same question (0)

All responses (8)

Answers (2)

Verified answer

Sukrut Parab 71,710 Moderator on at

Like (1)

Report

Answer to your questions

1. Yes , you will be creating single deployable packages for all your models including any isv packages.

2. That's correct . Always deploy package containing already existed models + your new models if any in your target environments. use build machine to create deployable package.

Was this reply helpful? Yes No
Verified answer

Sergei Minozhenko 23,093 on at

Like (1)

Report

Hi Rhushikesh,

1. Yes, you need to create one package for all custom models and ISV packages

2. Yes, it's correct, but if I understood correctly you will receive the error that deployable package is missing models already deployed to Sandbox and you will not be able to deploy it.

Was this reply helpful? Yes No
Rhushikesh R 758 on at

Like (0)

Report

Thank Sergei,

I do receive the warning pop up as of now whenever I deploy my only one customized model package out of 5 customized models.

The warning says that, remaining models are missing from the package. But that does not stop me from deploying the package.

So did you mean in coming features rollout I won't be able to deploy in the way I am currently deploying it?

Was this reply helpful? Yes No
Suggested answer

Deekshit Addepalli on at

Like (1)

Report

Correct, the AIO package is what you need which should contain all the packages that your environment needs to contain. If you do proceed with applying a package that only contains the new model or an updated model, then it will effectively uninstall the other models as mentioned in the documentation.

Was this reply helpful? Yes No
Suggested answer

Sergei Minozhenko 23,093 on at

Like (1)

Report

Hi Rhushikesh,

Yes, That the concept of AIO package to have all models to be deployed in one place. It's also needed to support self-service infrastructure

"You will need to provide a combined deployable package for customizations. That is, all custom extension packages, including ISV packages, must be deployed as a single software deployable package. You will not be able to deploy one module at a time. This was always a recommended best practice and is now enforced."

docs.microsoft.com/.../infrastructure-stack

Was this reply helpful? Yes No
Rhushikesh R 758 on at

Like (0)

Report

Thank you Sergei, Deekshit and Sukrut.

One last question, so is there any specific deadline for the enforcement? What I understood is it will be done in phases which is mentioned on standard document.

So does that mean before October 31, 2020, I should deploy one package which will contain all the customized models including ISV?

Or as of now I don't need to deploy it and I just need to take care of this thing while deploying my next custom package?

Was this reply helpful? Yes No
Suggested answer

Sukrut Parab 71,710 Moderator on at

Like (1)

Report

Yes on Oct 31st the extended support for this request ends . It always better to put a practice of deploying one package anyways instead of waiting for it to happen. You can deploy your current package and from next onward make a habbit of including everything in a single package.

Was this reply helpful? Yes No
Rhushikesh R 758 on at

Like (0)

Report

Thank you Sergei, Deekshit and Sukrut for your valuable replies. :)

Was this reply helpful? Yes No