web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Answered

Deploying selected models only

(0) ShareShare
ReportReport
Posted on by 126

We have multiple custom models and all of them were already deployed to the test environment. If changes are done to only specific model, is there a way to deploy only that model. We tried to create a code package with only specific model but upon applying it to sandbox via LCS, it gives warning that other models will be deleted.

Is there a work around to build code package and apply only selected model.

I have the same question (0)
  • Suggested answer
    nmaenpaa Profile Picture
    101,172 Moderator on at

    You said that you changed only one model. So what problem would you have if you deploy all your models?

    As you already found out, you must always deploy all CUS + ISV models as All-In-One deployable package.

    If you want to deploy only a subset of changes that you have made, you should manage it via separate DEV and MAIN branches in your Azure DevOps source control. Develop in DEV branch, merge the things that you want to deploy into MAIN branch, and create the deployable package from MAIN branch.

  • Verified answer
    Martin Dráb Profile Picture
    240,538 Most Valuable Professional on at

    You can't do it anymore.

    Even if it was possible, what would be the benefit? The deployment process is the same regardless of whether there is a single model or five models.

  • AR01 Profile Picture
    126 on at

    I wanted to save some model build time. Thanks Martin and Nikolaos, I get your point.

  • Suggested answer
    nmaenpaa Profile Picture
    101,172 Moderator on at

    Well, you should anyway always run a full build of your customizations when creating a deployable package.

    You should also use a build pipeline to create your deployable package, but based on your comment, you're not using one. Instead you seem to be using Visual Studio to create a deployable package of whatever local code you happen to have on a development VM. My strong suggestion is to set one up a build pipeline as soon as possible. This way you can always be sure that you know what's going to be deployed and can track it via ADO.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Women in Power Builds Momentum

Expanding mentorship, skilling, and AI innovation

Congratulations to the July Top 10 Community Leaders

These are the community rock stars!

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

#1
Martin Dráb Profile Picture

Martin Dráb 345 Most Valuable Professional

#2
CU10121822-0 Profile Picture

CU10121822-0 304

#3
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 283 Super User 2026 Season 2

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans