Relation between model layer and deployment package

(1) Share

Report

Posted on by CU03091226-0

115

Assume I have 2 models, ModelA and ModelB. In ModelA, I have added a new field in the CustTable form, in ModelB I have added a new field in SalesTable. These 2 models are independent and have no reference to each other only a reference to the Application Suite model. I want to deploy them on the sandbox i have, I created the deployment packages and deployed ModelA but when deploying ModelB I get an error that there is a model missing ModelA. Why can I not deploy models separatly if they do not event reference each other? Is there something related to the layer in which they have been created (usr currently)? If yes, what layer should they be to be able to deploy them as standalone packages.

I have the same question (0)

All responses (7)

Answers (1)

Suggested answer

Martin Dráb 237,967 Most Valuable Professional on at

Like (0)

Report

You deploy the whole application, not individual models. Therefore if you're deploying ModelB only, you're deploying an application consisting of a single custom model, ModelB. ModelA isn't included and won't exist in the environment. But the system noticed that there was ModelA before and prevents you from deleting it (unless you perform some steps to explicitly remove it), because you're likely doing it by mistake. Which is indeed the case.

It has nothing to do with layers.

Was this reply helpful? Yes No
CU03091226-0 115 on at

Like (0)

Report

Can you please elaborate more on the notion of deploying an application and not a model? Am i deploying then the solution that I created in visual studio? And is there any way for me to deploy for example a solution with a certain model without referencing another, or should i always use the All-in-one deployable packages?

Was this reply helpful? Yes No
Martin Dráb 237,967 Most Valuable Professional on at

Like (0)

Report

Visual Studio solutions and projects are used only for development; they play no role in deployment.

You builds model (or - more precisely - modules), which generates things like DLL files. Then you take compiled files of all the models that you want to have in the target environment and create a deployable package with them. All these things are normally done by a build server; you shouldn't do the build locally and select models manually.

Then you use this deployable package to install the application in an F&O environment.

Was this reply helpful? Yes No
CU03091226-0 115 on at

Like (0)

Report

Could you please provide documentation as to how to deploy new packages? I currently modify what i need from visual studio and create a new deployable package while selecting the packages, then upload this package zipped folder to LCS asset library and apply updates to target environment. But you have not answered my question regarding how to only deploy 1 package for example and not select all packages from VS.

Was this reply helpful? Yes No
Martin Dráb 237,967 Most Valuable Professional on at

Like (0)

Report

I think I already did answer it in my previous reply. You seem to want to deploy ModelA only, then ModelB only and have both ModelA and ModelB in the target environment, but you can't. If you want to have both, you must deploy both. You can deploy ModelA first and then ModelA+ModelB, but deploying ModelB only means that ModelA wouldn't be there, which violates your requirements.

If you decided you don't want to use ModelA anymore, you could tell the system to remove it (see Uninstall a package). But according to what you said, this isn't your scenario.

Here you have documentation for building the application using Microsoft-agents. An alternative would be using your own build VM.

Was this reply helpful? Yes No
CU03091226-0 115 on at

Like (0)

Report

So if i already have a deployment package on the environment containing ModelA and I want to deploy ModelB without removing the previous model, i would need to deploy ModelA+ModelB, deploying ModelB package alone is not doable whatsoever correct (unless i remove it)?

Was this reply helpful? Yes No
Verified answer

Martin Dráb 237,967 Most Valuable Professional on at

Like (0)

Report

Yes, if you want have ModelA in the target environment, you must include it in the deployable package. The deployment starts with an empty environment and install the content of the deployable package; it doesn't keep models that you have in the environment before. Always think about the target state; if the target state is an environment with ModelA and ModelB, your deployable package must contain ModelA and ModelB.

Then error is there just to prevent you to delete models by mistake, as you would do.

Was this reply helpful? Yes No

Join the conversation

Community site session details

Relation between model layer and deployment package

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

Featured topics

Product updates

Community site session details

Relation between model layer and deployment package

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Subscribe to this forum!

Select categories

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

Featured topics

Product updates