Dual Write should support the renaming of the FSCM unique record key
Dual Write should support the renaming of the FSCM unique record key. However, Dual Write does not sync the changes in the unique key field from FSCM to the Power Platform. This leads to data duplication and data inconsistency. For example, if you rename the Customer Account Number, this change...
warning when configuration key is disabled for entity data source
We wanted to use an entity InventWarehouseInventoryStatusOnHandEntity to expose data for our EDI solution however the entity exports 0 rows. Upon investigation and a lot of wasted time on customer and Microsoft side it was found/logged by Microsoft that Symptom: When exporting the data entity ...
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.
Upsert feature for OData service endpoint
Please support/implement the „upsert“ functionality for the OData service endpoint. (According http://docs.oasis-open.org/odata/odata/v4.0/e...
Implement retry logic when using BYOD with serverless database.
Currently BYOD export official document only support DTU model.
However more customers start using serverless database to match with their business operation. However, it now raises an issue where the first time serverless database is woke up by F&O it will return connection e...
DIXF should classify sensitive fields when exporting to BYOD/ADLS
Azure security recommendations has a feature which classifies database table columns with sensitivity based on the field names (so it's not super accurate). https://docs.microsoft.com/en-us/azure/azure-sql/database/data-discovery-and-classification-overview#discover-classify-columns Dynamics has...
Provide a summary of DMF execution error messages
Currently, error messages in DMF are only displayed in the Staging Data form and only for individual rows. It is difficult to get or provide an overview of errors, especially on larger imports. Provide a error message summary (on a separate tab on the staging table data form). I've been summar...
Thanks for the ask. We are reviewing this and one approach could be to expose the errors as an entity. This can then be used in PBI for error analysis.
Data Management - Refresh mapping of all entities
After each code release, it is necessary to perform the function "Refresh mapping" for each customized entity with new fields. The new feature would make it as job in the background for all existing entities. The existing changes to the mapping (validation deactivated, deleted assignment) should ...
Allow to specify a new file for an import without having to specify the entity again
When testing, or developing, you often need to load a new version of a sourcefile in Data Management.
Right now, you cannot just replace the existing file, you need to re-specify the entity, then browse to the file, step through 2 dialogs and then you can rerun the import.
...
OData - Aggregation support as per the OData standards
Aggregation support such as Sum as per defined in the OData standards would be really help...
Thanks for asking for this. Once we have F&O data in Azure Data Lake (ADL) as part of the work for October 2019 release, such scenarios should be handled by lake. We can revisit this topic if ADL will not meet this requirement.
Thanks.
Administrator
Thank you for your feedback.
We are not considering the suggestion at this time due to the following reason:
There is only one vote for this idea. Although, this is a fair ask, due to several competing work items, we will not be able to consider this until there is a larger ask.
Sincerely,
Sunil Garg
Microsoft.