Data events - introduce indication of the order of events (or guarantee order of delivery)
When running tests with Data events we discovered that order is not always consistent with inserts/updates happening in F&O.
I have created custom Table with Entity on top of that; the Data Event is sending CUD messages to Azure Service Bus Queue.
Running code to perform 1xinsert a...
Last Login Data
Currently, there is a bug within the Last Login Data form in D365 F&O where it doesn't always report the true date. My understanding is that the form is going to be deprecated instead of fixed. There is no option to review the last 90 days of login data to develop against in order to auto-de...
Add Created and Modify fields to all Data Entities
This information is extremely useful for audit reporting. Where available the following fields should be included on all data entities:
CREATEDDATETIME
CREATEDBY
MODIFIEDDATETIME
MODIFIEDBY
Recurring Batch Job to clean up Execution history/ staging data
I would like to have Batch Job to clean up staging data for all Import and Export Projects. Customers will run this periodically by specifying period(from date and to date).
1. Customer schedule Batch job with From date and To date
2. Batch Job when run withhold existing w...
Thanks.
Azure Service Bus Interface
It would be ideal to light up Azure Service Bus as a means for import or export of data. This is great for recurring integrations inbound or outbound. We build this on every implementation however it would make a great addition to the standard product.
Using data entities we...
Batch oData calls to D365 F&O API's should follow the oData protocol and return the first error
When calling multiple oData requests within a batch request which contains a final oData action call F&O will not return any errors prior to the oData action but instead run the action and return the result from that.
This is does not follow the oData protocol which is that th...
OData calls on full table before finding intended record
When Using Logic App with OData integration, to call certain records on any Data Entity, action takes longer than expected as the OData collects the data entity data as a whole, then starts the method used which results in a longer time taken than any other integration method used. if possible...
Request to add a feature of importing Planned order
It is unable to import Planned order from the data management. However, it is able to export Planned order. Once to check the proparty of the target entity "ReqPlannedOrderEntity" which is "Planned Order" entity from AOT, "IsReadOnly" propatiy was Ture. Please consider to become able to import P...
Synapse support for full export of ValidTimeState enabled tables on D365FnO
MS Announced Synapse doesnt support full export of ValidTimeState enabled tables on D365FnO. eg HcmPositionHierarchy , HcmEmployment.
To be able to move our reports to Synapse deltalake datasources we need this support immediately.
At the moment it is impossible to develop retros...
Change start time and end time in Data Management to real running time
Currently, Start time and End time which was show up when we import and export data entities are the time of internal import/export process, not the time where customer are truly experience. In example, Customer start an import project and it's take about one hour, but follow Start time and En...
Thank you for your feedback.
We are not considering the suggestion at this time due to the following reason:
We are currently working on data feeds as the new design for import/export. We will take your feedback into account in the new design and ensure the job execution times are calculated properly.
Sincerely,
Sunil Garg
Microsoft.
Administrator
Thanks for the product idea for improving data events! We'll continue to gather votes and feedback on this feature to help us prioritize it for a future release.