Allow custom fields to be distributed to channel database without extensions
In D365 F&O it is now possible to add new fields directly from the UI. Like adding a new field to the customer. I see that we can add this field manually to the sub-scheduler jobs, and also add the field to the schema. It would be nice if this also was supported in the channel database, and mo...
Support product attributes in sales quotations (like in sales orders)
It is possible to extend the POS(call center to handle attributes in a sales order. Related docs article regarding this particular feature: https://docs.microsoft.com/en-us/dynamics365/unified-operations/retail/dev-itpro/order-attributes Unfortuantely those retail attributes are not available f...
Hybrid data fetch in MPOS
MPOS should have hybrid data fetch model where it should retrieve all the master data from offline when supported.
Allow filtering of data within a data group during CDX syncronization
Currently, if any data is different per channel (e.g. customers) and there is a legal or privacy reason they cannot exist in every channel, then data groups cannot be used.
This has significant impact on performance as the only alternative at present is to have a separate data group pe...
Offline DB to have a separate schema to channel DB
Offline DB may not always have the same requirements as the channel DB.
Currently the two are interlinked and it is difficult for an ISV to add and control their content for the offline scenario.
This will also impact bandwidth usage for a store given the same package...
Allow Offline Data to be synchronized on a different schedule from the channel DB
Currently the offline Data packages for a register are created on the same schedule as the channel DB.
This increases the bandwidth requirements from a store perspective (especially with an RSSU in place).
Allowing a different schedule (data group?) for the offline DB allows fl...