Share
Report
2Hello Community,
I am working on a CRM project that includes several components, and I need guidance on the best practices for packaging and delivering it. The project involves:
- Dual-write table mappings between CRM and Finance & Operations (F&O).
- Custom plugin assemblies and plugin steps.
- Business process flows (BPFs) and other customizations.
- Integration of custom F&O logic tied to CRM.
Here’s the approach I’m considering:
- Prepare a managed solution in CRM, including all custom tables, plugins, subgrids, and business process flows.
- Add the dual-write table mappings to the solution (via Add Existing -> More -> Other -> Dual Write table map).
- Export the CRM solution as a managed package (.zip file).
- Create and package the F&O logic separately.
- Deliver both the CRM and F&O packages to the customer.
For installation, I plan to:
- Import the CRM solution via the Power Apps portal.
- Apply the CRM package for dual-write mappings via the F&O dual-write page.
- Install the F&O package as per standard procedures.
Questions:
- Does this process align with the recommended delivery approach for such projects?
- Are there specific considerations or best practices I should follow for dual-write mapping integration and dependency management?
- How can I ensure a seamless deployment without dependency or compatibility issues?
All responses (
Answers (
