Scenario – Integration between finance and operations apps and Customer Engagement apps
You can create the customer in finance and operations apps and Customer Engagement apps. You’ll create vendors and products in finance and operations apps, but they should also be available in customer engagement apps. Additionally, you can add more information in Customer Engagement apps.
Patterns
Consider the following patterns (best practices):
- Use dual-write integration. Verify if the current dual-write templates cover the scenario (for example, integrated customer master, vendor integration, product integration) or if you can extend them for your needs.
- Evaluate the scenarios in which dual-write isn’t triggered (for example, cross-company data sharing).
- Consider virtual entities when dual-write isn’t applicable.
Further information
Use out-of-the-box capabilities when they’re suitable for your needs. For example, for complex mapping based on business rules, you might need custom integration. Avoid mastering data in multiple systems if possible. Consider defining master at the field, if not entity, level. Otherwise, you should design for conflict resolution.
Anti-patterns
Consider the following anti-patterns (pitfalls):
- Design a custom integration immediately.
- Use dual-write for multiple Dataverse instances.
- Mix dual-write and frameworks, which aren’t compatible with dual-write.
red hat certified specialist in red hat enterprise linux diagnostics and troubleshooting malaysia