Hi,
It is a very interesting question, but when we started integrating both system a long time ago (CRM NAV ) over the old connector and then through the native integration, coming finally to the native integration on BC, the view was always that any operation that has a financial effect, should be done on the ERP side and nt the CRM side, so the CRM side is a system meant to be a repository for all the (relationship management) information, like quotations, account and account transactions, prodcuts infos and so on.
But when it gets more to your inventory and the nventory movements that give real financial movements in the background that require the existance of a COA, this is exactly the time where you should be on the ERP side.
That's why when we designed the native integration, we though of the coupling Idea, which means your products exist in CRM physically, but get coupled with Items on BC, so as you can do on CRM side all the transactions you ned, and they get translated to financial like movements in BC.
TO understand this more, please have a look on the concept of the native integration (CRM to NAV) wich is the same for (CRM BC):
docs.microsoft.com/.../integrating-dynamics-crm-in-dynamics-nav
Product
Item and Resource
In Dynamics NAV:
Create and couple a new product in Microsoft Dynamics 365 for Sales from an item or resource in Dynamics NAV.
Access a coupled product in Microsoft Dynamics 365 for Sales from an item or resource in Dynamics NAV.
Manual and scheduled data synchronization from Dynamics NAV to Microsoft Dynamics 365 for Sales.
In Microsoft Dynamics 365 for Sales:
Access an item or resource in Dynamics NAV from a product in Microsoft Dynamics 365 for Sales.
I hope this explains it.
Thanks,
Rahman
