Notifications
Announcements
No record found.
Hi all
I am receiving the following error on all records when trying to upload new vendors.
Results. update not allowed for field 'RetailVendTable,AccountNum'
We are currently on version 10.0.32 and do not use the retail module. Has anyone seen this before and been able to resolve?
Hi, RetailVendTable datasource is added in VendVendorV2Entity in 10.0.32 (or 10.0.31 or 10.0.30), as its not existing in 10.0.29.
Can you check if any field specified below is filled in your file. If yes, then try clearing the field and uploading one record.
Hi Mohit, thanks for your response.
We don't have any of those fields in our file. We have uploaded with VENDORACCOUNTNUMBER, VENDORORGANIZATIONNAME, VENDORGROUPID, DEFAULTLEDGERDIMENSIONDISPLAYVALUE and ONHOLDSTATUS columns and still receiving the error.
Can you confirm about the Customization done on that entity?
No customisations have been done on that entity. It is the standard Vendors V2 entity.
You can try exporting Vendors, download the file, delete all records and add a new record to import. If still does not work, try raising ticket to Microsoft with reference to below MS Fix.
https://fix.lcs.dynamics.com/Issue/Details/1313712?bugId=804953&dbType=3&qc=7b58519797a41272b0b4216010005749acea775dadec9e16bf6778865bc8596d
Hi. I am on the Power Platform development side and with a recent release (I am waiting to hear back what version from our D365 F&O team) I am getting the following error when executing an update record via microsoft power automate using the VendorsV2Entity:
An error has occurred. Write failed for table row of type 'VendVendorV2Entity'. Infolog: Error: Cannot locate data source record of type RetailVendTable with RecId #####. Entity name: VendVendorV2Entity, RecId: ######, Database operation: Update..\r\nclientRequestId: xxxxx"
We also do no use retail. No solution, but maybe rings a bell if anyone has run into similar issue?
We had the same problem, and we are not using the retail module. I can confirm that applying the quality update 10.0.1549.91 resolved the issue.
WeepingAngel, I had the same problem, I applied that same update and it fixed the problem. Confirmed!
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
As AI tools become more common, we’re introducing a Responsible AI Use…
We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
André Arnaud de Cal... 449 Super User 2025 Season 2
Martin Dráb 422 Most Valuable Professional
BillurSamdancioglu 239 Most Valuable Professional