Share
Report
98Hi All,
as we all know we can deploy using command line deployable packages for all one-box D365 environment , can we do the same on on-premises without going through the LCS preparation and download stage ?
i asked chatGBT and found below answers if anyone can advise please:
No, you don’t necessarily have to deploy all previous customizations when making a small change, like modifying one field in a form. However, the deployment process in an on-premises environment can be tricky. Here’s how you can optimize it:
1. Deploy Only the Modified Model
Instead of deploying all previous changes, you can generate a deployable package that includes only the updated model. Steps:
- In Visual Studio, select the model that contains your change.
- Build and create a deployable package only for that model (not the whole environment).
- Deploy this smaller package through LCS or manually via PowerShell.
2. Use Hotfix Deployment (Metadata-Only Packages)
- If your change doesn’t require a database update, consider deploying a metadata-only package rather than a full application package. This significantly reduces deployment time.
3. Skip Database Synchronization (If Possible)
- If your form change doesn’t require schema modifications, you can skip database synchronization during deployment to save time.
- Use PowerShell to manually apply changes without full re-sync:
4. Deploy Using PowerShell Instead of LCS (For Faster Deployment)
- Instead of LCS, which takes longer, you can manually deploy the package using PowerShell:
- This is faster because LCS adds extra validation and processing overhead.
5. Use a Local Asset Library
- If using LCS, upload the package to a local asset library instead of downloading from the cloud every time.
Would you like help generating a minimal deployable package for your change?
Install-AXDeployablePackage -PackageName "YourPackage.zip"Install-AXDeployablePackage -PackageName "YourPackage.zip" -SkipDatabaseSync
Categories:
I have the same question (0)
All responses (
Answers (
