D365 F&SCM ISV Installation Guide
Important
- The Version 60 release moved to a zero-license model.
- You should remove the license files from your source control to ensure they are not included in any deployable packages generated by your pipelines.
- Failure to remove the applicable license files results in an error, the deployment failing, and an automatic rollback.
1| Prerequisites
The installation process should be the same as any D365 ISV product from Accenture. Any product-specific information will be noted at the appropriate step.
If this is a new development VM, we recommend building the VM fully before installing (including provisioning the admin account).
This guide focuses on installing a D365 ISV product from Accenture into a development VM (or additional development VMs).
Creation/management of build, UAT, and production environments should follow the standard Microsoft documentation/process.
If there are any questions or concerns about the steps listed in this document, please reach out to Accenture for clarification.
2| Installation into a Development VM (First VM)
The initial development VM needs the following steps:
- Install the deployable package provided by Accenture (should be a zip file): https://docs.microsoft.com/en-us/dynamics365/unified-operations/dev-itpro/deployment/install-deployable-package
- The deployable package will include the solution package/model and the license package/model.
- The deployable package will include the solution package/model and the license package/model.
- Synchronize the database.
- Add the product and product license folders to your source control in Visual Studio. You will not see your objects in pending changes until this happens.
- Some items might be excluded; make sure you include all items.
- The following Microsoft write-up should be followed. Again, make sure you select both the product and product license package folders.
- https://docs.microsoft.com/en-us/dynamics365/unified-operations/dev-itpro/dev-tools/manage-runtime-packages
- Check in your ISV product.
3| Installation (Additional Development VMs)
- Map the product and product license folders to the appropriate local folders from source control.
- Get the latest.
- Sync database.
4| Common Errors
- Be careful about having spaces in the file path or name.
- After all steps are completed, verify that the product package and product license package have been added to the source control explorer under the Metadata file.