The PSTL Vendor Name Modifier returns the following errors in GP2016 and GP2018. Invalid column name 'VendorID' and smitemcahnge1 return DBMS 207. How can this be fixed so the PSTL Vendor Name Modifier functions correctly?
*This post is locked for comments
Scott,
Right now there are no official workarounds for this in GP 2016.
The issue came down to a cursor in the smVendorNameChange1 stored procedure that finds all tables that have the 'VNDCHKNM' column and updates them based on the VENDORID value. The problem is that the CM20200 and CM20300 tables have 'VNDCHKNM', but do not have 'VENDORID' columns, which leads to the error you're seeing.
This stored procedure is encrypted, but if you have a way to update it you could exclude the CM20200 and CM20300 table from the cursor to get around this issue.
Lucas,
Thank you for the update.
Are there any work arounds or hacks for GP2016?
Scott
Scott,
This is something we're aware of and it should be addressed in the upcoming GP 2018 R2 release. There are no plans to port the change back to GP 2016 at this time.
Sorry for any inconvenience that this has caused. Let me know if you have any questions..
Sandip,
I was not even using an import file. I tried entering one vendor name change on the Vendor Name Modifier window and the name change failed with the indicated error messages.
Thank you,
Scott
Hello Scott,
Is it CSV file or Tab Delimited file. Can you please check with Tab Delimited file it works or not? Plus you must mention correct heading column name.
Thanks much
Sandip
Share
Report
All responses (
Answers (
18,297