Announcements
No record found.
Hi All,
Is there only one way to deploy package on D365FO ?
i mean VS > D365 > Deployment > Create deployment package.
Please give me more shed on this.
Thanks!
Hi,
The navigation path that you mentioned "VS > D365 > Deployment > Create deployment package" will create deployable package.
If you want to move code between dev environments, you can install package or use source control.
Thanks Arun
as you said "If you want to move code between dev environments, you can install package or use source control."
Can you please provide me some link on this.
please give me more shed on this.
thanks!
Hello ,
Your question talks about creating deployable package, and not moving code between Development environment.
Could you please, tell us which one you want to achieve ?
As Arun said, that's why I am asking to provide me some link to know the process. What is wrong here? Now I come to the original question, that i understood.
Very simple thing you do not understand. Simply escalating
Instead of this, better if you know the answer please provide. So, that I will close this thread. Other will get benefit
thank you
Hello,
Please, this is a forum, and you should try as much as possible to describe what the issue is. It is in the best interest of all of us not to waste time. The aim of the forum is to help one another while being professional. :).
To move code between environment, you can commit your code from environment A via Azure DevOps and restore in Environment B.
learn.microsoft.com/.../version-control-metadata-navigation
Another option is to export and import .axpp files.
learn.microsoft.com/.../projects
Yes Komi, I know this is forum and everyone is watching this. I already described earlier my issue in very simple way. Based on your reply I answered.
Anyway leave it, thank you
Hi @rp@n,
Please, do you think, the answers provided by myself and Arunraj where really helpful?
When I read the question, you tried to create a deployable package. Note the option you mentioned in your initial question is one option, but not recommended if you want to release software.
Recommended would be using different branches. Move only the approved and tested changes to a release branch and create a deployable package via Azure Pipelines. Create deployable packages in Azure Pipelines - Finance & Operations | Dynamics 365 | Microsoft Learn. If you do it via Visual Studio, also work in progress which is on your dev machine will be added to the deployable package with possible unexpected results in a customer environment.
Thanks Andre
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.
Congratulations to our 2026 Super Stars!
We are thrilled to have these Champions in our Community!
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Giorgio Bonacorsi 663
André Arnaud de Cal... 439 Super User 2026 Season 1
Syed Haris Shah 337 Super User 2026 Season 1
