This is NAV2009 SP1, build 29626 on SQL Server 2008. Take any field, and rename the field in the table designer. Save/compile and try to modify a record. We're getting an 'invalid column name' SQL Server error on the old field name.
Take for instance the Description field in the Currency table and change it to "Description Test". It saves and compiles properly. Then open the table from the object designer and change any description. We're getting an error saying "207,"42S22",[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'Description'.". Note that at this point, the column name is actually "Description Test", so it is referencing the field name that it used to have.
The field name in NAV is "Description Test", the column name in SQL Server is "Description Test", keys are updated properly, SQL indexes are updated properly, we've looked everywhere we could think of. Somehow, NAV retains the old field name somewhere, but we can't figure out where.
0
Answers
Is it a problem you have with only that version or also with other versions? If it is only that version, it could be a problem of the build.
No PM,please use the forum. || May the <SOLVED>-attribute be in your title!
Don't know if that might be your problem as well. I added the database name to my icon so I never logged in "incorrectly" again.
The problem we're facing is figuring out where the heck it saves the old field name. The query coming out of NAV must get it someplace, but everywhere we look the new field name is used.
RIS Plus, LLC
RIS Plus, LLC
If it helps, it means the old version is still kept in memory somewhere.
No PM,please use the forum. || May the <SOLVED>-attribute be in your title!
RIS Plus, LLC
RIS Plus, LLC
BTW: can you replicate the problem on another server? Like a VM with that windows and SQL in it.
No PM,please use the forum. || May the <SOLVED>-attribute be in your title!
RIS Plus, LLC
MVP - Dynamics NAV
My BLOG
NAVERTICA a.s.
RIS Plus, LLC
2009 sp1 sql 2008 on Currency table and it worked fine.
Also are you on enhanced security model? And has security been synched?
Independent Consultant/Developer
blog: https://dynamicsuser.net/nav/b/ara3n
I haven't been able to reproduce on Cronus, it seems to be a database specific problem. It's a 4.0 database, exe upgrade to 5.0 SP1, SQL restore to development server, exe upgrade to 2009 SP1, imported objects upgraded to 2009 SP1 and that's when the problem began. I reproduced that situation on Cronus and could not recreate the issue. I think there's a MSFT support ticket for it now, if I am updated about the progress I'll follow up.
RIS Plus, LLC
So, lesson learned: if you run into problems like this, check the triggers on SQL Server :thumbsup:
RIS Plus, LLC
Except in my situation, the users had renamed the company, and suddently could not enter data on one of the req line.
Independent Consultant/Developer
blog: https://dynamicsuser.net/nav/b/ara3n