Joerg Rau Head of Dynamics 365

When running a report, a user can choose a filter for the pre-defined fields or replace an existing filter field with a new one, but a user can't add additional filter fields. For example, the Inventory Valuation report offers three field to filter on. Let's say the user makes use of these three fields but requires now a fourth field to filter on. This is currently not possible.

If you want to enhance or modify the integration or field mapping then you need to develop an extension (app). In order to get/see the enhanced mappings, you have to click on the "Use Default Synchronisation Setup". This function deletes all mappings and adds then all mappings from all extensions. This might be OK for the very first deployment but in an existing environment where default settings have been changed, match coupling rules have been setup etc. it will wash away all these settings and can cause synchronisation chaos.

It would be great to keep all existing settings when adding a new version of an extension enhancing the integration even further.

One approach could be to have a snapshot the current settings, refresh all mappings as currently done, and then re-applying changes from the snapshot. Some will not be possible if for example an integration was removed in the extension etc. This could be shown with a conflict list so that the user is aware of what wasn't been able to apply.

The standard Table Integrations for Datverse and Dynamics 365 Sales should include the Business Central SystemID and map this with the appropriate ID (Primary Key GUID) field of the Dataverse / Dynamics 365 Sales table. This would allow for better coupling and would avoid the issue when a user renames a field, which is easily done in Dynamics 365 Sales.

There is often the requirement that a significant amount of users have to create occasionally a Purchase Order. That's all they have to do in Business Central. Currently, they would require a Full User license. Given that they are only occasional users, they would fit best as Team Members. As a Team Member, you can create a Purchase Quote and not a Purchase Order.

Workarounds are in place by either implementing a separate purchase/procurement system or converting quotes to orders etc.

Instead of selling more full users, we see the opposite of selling no or fewer licenses due to work around. More licenses could be sold if creating Purchase Orders would be part of the Team Member license.