Sunil Garg PRINCIPAL GROUP PROGRAM MANAGE

If I setup a BYOD export job with DMF, and schedule it to run say, every hour, but for some reason one of the exports takes over 1 hour, then a second instance of the same job kicks off regardless. This then attempts to export the same data but with slightly less resources. This will undoubtedly also take over an hour, so the problem compounds. There is an option on the "Export job in batch" window for "Run Sequentially" which might seem related, but it doesn't appear to work for exports.

Whenever D365fO is exporting data to Bring your own database, the available fields in the target tables is fixed to the fields being available in the related Data management staging table. + [EXECUTIONID] + [DEFINITIONGROUP] + [SYNCSTARTDATETIME]. In order ro allow LogicApps to be triggered on INSERT of a new record, the table will require an IDENTITY column. In order to allow LogicApps to be triggered on an UPDATE, a ROWVERSION column. It would be wonderfull, if all tables created in BYODb would have these two columns. https://flow.microsoft.com/en-us/blog/introducing-triggers-in-the-sql-connector/

Exporting data to BYOD fails if password contains double quotation. Since Error message is [An Error occurred in add data flow component for Entity Store], finding root cause is very difficult. Double quotation is not prohibited characters in connection string. Please fix this issue as D365fO bug.

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 sender to understand what was missed. With numerous sources per end point, we would benefit if it was possible to add some free text to the message queue form that we could fill while importing. We would add some additional information about the message to help with the finding of the source and better understanding what the message was. e.g." SourceSystem:MasterCard sourceFile:erp1.txt"

There is no way to import for Resource (WrkCtrTable). So, please consider to add a feather to import for it.

It would be really useful for a consultant if they could manage all D365FO entities without the need of a developer. This should be achievable through the User Interface rather than Visual Studio. - you should be able to view all entities within the system regardless of the enable data management / ispublic status's - for any entity you should be able to disable/enable it for data management or odata consumption. - have the ability to create a new data entity from a list of data tables.

Please, give us possibility to refresh entities by batch. Run refresh is needed after each update (ISV, etc.) and it is often forgotten.

Navigating to: Data Management workspace > Import tile > +Add file button This dialog is set up such that the left column has options to choose your source file or spreadsheet, while the right column has you specify which data entity it will be importing to. The problem with this is that Dynamics won't let you upload a file unless you have already specified the data entity to which it belongs, so the dialog has to be executed right-to-left, i.e. (+Add file button, right to the Entity Name drop down, down to the source data format dropdown, then back left to the Upload and add button). So in essence you're zig-zagging all over the place) It is counter-intuitive to have dependent controls positioned to the left-hand side of the needed control. The dialog should be redesigned to where you specific the entity first (i.e. have that on the left hand side), and then the upload and add button to the right of that.

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.

We got many cases that customer regularly backup their Database from PROD. They have noticed the Database size is growing too quickly. We have found out that customer got a lot of export jobs and it increases records in the staging table and causes the Database size growth. A customer can run cleanup staging from Data management by manually. But exports happening every frequently so it’s hard to keep on top of those. We would like to run a function cleanup staging as a batch so we can save more time.