In D365 F&O, standard functionality allows a Vendor record to be deleted from the system as long as no transactions have been posted against the account – with one notable exception. This exception occurs when a Vendor record is mapped to a Worker record (Worker to Vendor Mapping on the TrvWorkerVendorMapping form).

When a Vendor record is created and then associated with an Employee/Worker, standard Microsoft code updates the below tables.

- DimensionAttribute
- DimensionAttributeValue
- DimensionAttributeLevelValue
- DimensionAttributeValueCombination
- DimensionAttributeValueGroup
- DimensionAttributeValueGroupCombination

Even though no transactions have been posted against the Vendor record/account – once records are created in these tables, the system no longer allows the Vendor record to be deleted.

The system will not allow the Vendor record to be deleted until the records pertaining to desired vendor are deleted from the tables referenced above. However, the since the standard code does not allow for the records to be deleted from the tables, the Vendor record cannot be deleted from the system.


DESIRED RESULT/OUTCOME:

Add logic to standard code to enable deletion of any Vendor record which does not have transactions posted against it. Specifically, modified standard code to allow for the deletion of Vendor records that have been mapped to a Worker record – if no transactions have been posted against the record.

I submitted a support ticket to Microsoft and received the following response: “This is an intended behaviour of application. The data is updated in the DimensionAttribute tables is immutable and cannot be deleted. Similar issue has been already reported to us earlier under the bug – 397836. We already have a deliverable for this scenario but it’s still under discussion stage. Request you please log this as a suggestion in ideas portal (https://experience.dynamics.com/ideas/) for this scenario. Based on number of customers votes our team can prioritize this scenario and might release in upcoming versions.”

Details of bug 397836 referenced in Microsoft's email: "Thank you for reporting your issue. We've researched this and learned that the fix is beyond the scope of a hotfix, or that it's a high-risk change. Because of this we are tracking this issue as a new feature rather than a fix. We'll evaluate the issue compared with other proposed enhancements. If this feature is scheduled for development, we'll communicate it on our Release plans site."