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

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Suggested Answer

deploy package on dev environment D365fo

(0) ShareShare
ReportReport
Posted on by 199

Hi,

I want to deploy custom package on dev environemnt, Anyone here who has done it before? 

Regards,

Zohan

I have the same question (0)
  • qianwang Profile Picture
    7,168 on at

    Hi ZoHan93,

    Please read this DOC:

    docs.microsoft.com/.../install-deployable-package

    Regards,

    QianQW

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

    Yes, it's possible.

    If it's a cloud hosted system you can apply the package via LCS. If it's a local VHD, you install it from the command line.

    Please remember that deployable packages don't have any source code. So the only scenario where you would want to install a (custom) deployable package to a dev system is that you are using some ISV solution, and they didn't provide you the models (source code).

    Can you share any details about your scenario?

  • Zohan_93 Profile Picture
    199 on at

    Nikolaos,

    Thankyou for your suggestion, There's a third party which have provide me a package to deploy it on dev server and then i moved it to UAT environment. Now the first question arises should i deploy the package via lcs just we did it when we are deploy package from Dev to UAT. Or is there's any command line procedure which i have to follow by doing deployment. I'm confused as i've never done deployment on tech server.

    Regards,

    Zohan

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

    You can apply it via LCS.

    Then add it to source control, and let your build process include it in the deployable package that contains also your custom code. This way you will have one deployable package that contains all ISV + custom code. Then apply this package to test/prod.

    docs.microsoft.com/.../manage-runtime-packages

    Having this "All In One deployable package" is already mandatory for self-service topology systems, and in October it will be mandatory for all kinds of sandbox / prod systems. Check the announcement in LCS for more details.

  • Mark JZ Yeap Profile Picture
    240 on at
    [deleted]
  • Suggested answer
    nmaenpaa Profile Picture
    101,162 Moderator on at

    Hi Mark,

    I'm sorry but I don't understand your question.

    Let's look it like this:

    In any customer project, all code (customizations and ISV solutions) for that customer must be in their Azure DevOps source control. No matter how you bring this code in (from ISVs, from other projects, or just writing it for this customer) it must always go to Azure DevOps.

    Then you have a build process that builds the code that you have added to source control, and creates a deployable package. This package is then deployed to UAT and Prod.

    If something is still unclear, just ask.

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

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

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

#1
Martin Dráb Profile Picture

Martin Dráb 503 Most Valuable Professional

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 434 Super User 2025 Season 2

#3
BillurSamdancioglu Profile Picture

BillurSamdancioglu 278 Most Valuable Professional

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans