Here are a few considerations to keep in mind while designing your integration solution for Dynamics 365 for Finance and Operations:

• Simplify the overall architecture and try to reduce the number of integrations between applications wherever possible. It is one of the areas that causes recurring issues in production.
• Clearly define the master system for each data element, even though you may have it stored in multiple places. In some cases, this may have to be defined at the field level. For example, a customer master is stored in CRM and Finance and Operations as well. CRM might be the master for all the customer information except the credit limit.
• Ideally, you should avoid duplicating data across multiple systems, although in some cases you cannot avoid it for business reasons or for systems to work. For example, customer records are required in both the CRM system and operations. However, you can opt not to integrate the CRM-centric customer information that may not be needed in Finance and Operations.
• Understand and document business SLAs for each integration; think through the impact in extreme situations. One of our customers had their inventory being refreshed into their e-commerce system every 2 minutes. This was fine until the Black Friday weekend. During that 2-minute window, they oversold a product that was being sold below its cost (they only wanted to get rid of the on-hand stock). However, the customer ended up buying more to fulfill the additional orders that were received due to the delays in inventory updates. It is important to understand SLAs and business impacts while designing integrations.

With this section, we have come to the end of this chapter. Now, let's summarize what we have learned!