RE: Application Objects Merge - License issue when importing
Hello,
You are correct, you cannot do this straight forward.
You must first include the new fields on your table.
To do this you must take FOB file of the table with the fields that are being added, import it in the database where the fields are missing, and in the conflict window select merge existing<-new.
This will add the fields to your table and will allow you to import your TXT file afterwards.
The error you are getting is a security measure from Microsoft. It is obvious, you cannot import a TXT file that has new fields in a reserved field range :-) Can you imagine the things you'd be able to do if that restraint wasn't there? But you can do it if the file is in FOB format, since there is not a way to modify a FOB file (unlike a TXT).
Secondly, you might run into an issue:
If you try to add fields using the method I just described, and the fields have code that refers to themselves (like on the OnValidate of a field that checks that the value being input is correct) you will get an error because NAV will test the code and will not find the field (it's natural, it hasn't been added yet). So you must do a two step process in that case:
1.- First delete any code related to that field (I use a tool I made, I have to create a blog post about it :))
2.- Export the table and import it again without that code.
I hope that clears out some of your doubts
Share
Report
2
All responses (
Answers (
