How to deploy an Entity in TEST sandbox

(0) Share

Report

Posted on by vannamani77

417

Hi,

I have a change set in devops which has only one entity. The name is EDIInventoryLevelEntity.xml. How to create deployable package for this so that I can import to Asset Library and Apply it In TEST sandbox environment.

Regards,

Manivannan

I have the same question (0)

All responses (14)

Answers (5)

Verified answer

nmaenpaa 101,160 Moderator on at

Like (1)

Report

I assume you have a build system set up. Simply start build in ADO, and you can download a deployable package from the build results once it's finished.

Technically you can also create deployable package in Visual Studio in Dynamics 365 menu but that's generally not the recommended way of deploying your customizations.

In either case, you should always build&deploy all your custom code. You can't deploy single objects such as data entities. Instead you build and deploy your entire package(s).

If you don't yet have a build system, now is a good time to deploy it. Your customer wants and expects professional application lifecycle management from you.

Was this reply helpful? Yes No
vannamani77 417 on at

Like (0)

Report

Hi Nikolaos, As shared in previous forums which you answered our previous development partner maintained the code in his DevOps and now he does not give support. I understand we need to have a new build system (DevOps) and we are parallel working on that. In mean time, Is there any shortcuts to deploy that Entity alone as a quick fix.

Was this reply helpful? Yes No
Verified answer

Satish Panwar 14,671 Moderator on at

Like (1)

Report

Interim fix.. don't use this once you are out of your emergency.

docs.microsoft.com/.../create-apply-deployable-package

Was this reply helpful? Yes No
vannamani77 417 on at

Like (0)

Report

Whether entity can be build in same way. My entity name is EDIInventoryLevelEntity.xml which is under Meta Data folder.

Was this reply helpful? Yes No
Verified answer

Sukrut Parab 71,710 Moderator on at

Like (1)

Report

Weather its one object or thousand objects deployment has to be done through deployable package in managed environments . The only option remains for you now is generate package through VS however you have to be careful about not including unwanted changes.

Was this reply helpful? Yes No
Satish Panwar 14,671 Moderator on at

Like (1)

Report

Hi Manivannan,

Do you block the responses be marked as answers. If so, why?

Was this reply helpful? Yes No
vannamani77 417 on at

Like (0)

Report

Hi. No I am not blocking any responses. I have only two options in my portal. 1)like 2) unlike and I always put Like to every reply.

Was this reply helpful? Yes No
Verified answer

André Arnaud de Cal... 301,037 Super User 2025 Season 2 on at

Like (0)

Report

When you create a new post, there is an option to select if it is a question or discussion. The discussion option was chosen. Then it is not possible to verify the correct answers.

I have changed this thread to a question type now.

Was this reply helpful? Yes No
vannamani77 417 on at

Like (0)

Report

Hi Satish.

I am referring to your link because its emergency to do package deployment in Development environment and need to move to PROD

docs.microsoft.com/.../create-apply-deployable-package

I need a clarification on the above link.

My developer worked on "ASP-DEV1" VM and moved the sourced code (Che**.xml) to TFS (Trunk > Main > Metadata > .. > che**.xml)

I have another VM called "ASP-BUILD1" VM. I logged in to it and get the latest from TFS. In this machine the Main folder are mapped to C:\Trunk\Main

The latest files got downloaded.

Now my question is in ASP-BUILD1 when I go to Visual Studio > Dynamics 365 > Deploy > Create deployable package and select model and create package it create package based on K:\AOS Service\

I doubt how my new code (Che**.xml) which is in C:\Trunk\Main will go to K:\AOS Service. I think it will not. Now how to solve this issue ? Should I manually copy the file ?

Regards,

Manivannan

Was this reply helpful? Yes No
Verified answer

nmaenpaa 101,160 Moderator on at

Like (0)

Report

Mapping the workspace to c:/Trunk doesn't make sense. You must always map the workspace in AOSService/PackagesLocalDirectory since that's the folder where Visual Studio tools will handle D365 source code.

You should not map anything in the build system, or do any manual code handling there. You will just risk messing up your future ADO based builds.

If you have a build system, just launch the build from ADO. If you can't do that because of some temporary situation, you should create the deployable package in a dev system, not in a build system.

Was this reply helpful? Yes No