-
Increase the limitations of 1000 records
we're facing an issue where the posting of journals job fails due to limitations on processing more than 1000 records per transaction during post migration actions. This affects collective updates on a high number of records under a single transaction, including posting movement journals and service order job approvals.
error message:
Unable to write data to entity msdyn_sharedproductdetails.Writes and CDS error code : 0x80060888 response message: The current change set contains too many operations. A maximum
(874ACF4A-F8F7-4584-B243-184FC2517382}For troubleshooting see https://go.microsoft.com/fwlink/?linkid=2244045. Activity ID for troubleshooting information on troubleshooting see https://go.microsoft.com/fwlink/?linkid=2244045 allowed in a change set. For information on .. number of '1000' operations are
we understand it's a limitation however it's affecting the business and the flow of the work as it's better to have all the functions with the same integration tool to avoid any data missing.
-
Reset button in Azure synapse link and error log button
in Azure synapse link and specially in fabric it would be easily to have a reset button to readd all the tables automatically and also to have a button for showing the error logs or the tables that are stuck or failing with incorrect state.
-
Need a detailed history form shows the progress of the archival jobs
we are facing difficulty to monitor the progress of the archival jobs, we faced an issue that the Dynamics 365 Finance Sales order archiving process via Dataverse long term retention is stuck and not progressing, remaining at the 'Reconciliation' stage for at least a week without any error message, and then it has been resolved from it's own without having logs for this progress.
-
Assign a contact via the contact for party record in CE should get linked to the correct account selected not to another account for the same party
When you attempted to create new contact party records( Associated contact) under the account record these newly created contact party records were incorrectly associated with a different account but with the same party ID, which basically by design behavior as the plugin step `Microsoft.Dynamics.GABExtended.Plugins.AssociateContactForParty` is part of the dual-write Party and Global Address Book (GAB) solution, which manages the association of contacts to parties (accounts, contacts, vendors) between Finance and Operations (FnO) and Customer Engagement (CE) systems. when adding a new contact for party record, the plugin links the contact to any prospect that has the same party ID, which causing conflicts, please consider changing this behavior.
