Data project with insert-only
New setting for data project / entities - insert-only. Sometimes we want to be sure that the same primary key is not received twice. Simple setting like this would ensure that the data is not manipulated with duplicates after received.
Offer data entity publishing and export to Azure Cosmos DB
At the moment the BYODB concept can only publish D365-FO data entities to an Azure SQL Database. Would be nice to also have an option to publish to a NoSQL Azure Cosmos Database in a configurable (no-code) way just as there is currently for Azure SQL.
Refresh entity list by batch
Please, give us possibility to refresh entities by batch. Run refresh is needed after each update (ISV, etc.) and it is often forgotten.
Data entity for payment terms translations
Request to have a data entity for payment terms translations. Current version of Dynamics 365 FO only supports a data entity for payment terms, but not for payment term translations
Additional infotext for Messages sent to inbound recurring integration queue (DMF)
In the message queue we have very little information or tools about the underlying message. Sometimes the inbound messages go to an error, file is lost and troubleshooting is required. Our only handles at the moment is the messageid and timestamp that is generated and we have to see from the send...
Transaction Financial dimensions uploader
D365 have many data entities, but also many areas in the system not covered with data entities. After import data, the customer must edit transaction line by line to update the Financial dimensions (very hard work) So, if we try to develop a tool to update the Transaction Financial dimension...
Automatic resequence
In Data Management > Copy into legal entity: When adding multiple data entities, the resequence is not possible in an automatic way. We have to try and sequence the entities manually. This is very time consuming. Why not propose an automatic resequencing ?