Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics NAV (Archived) / Application Objects Me...
Microsoft Dynamics NAV (Archived)

Application Objects Merge - License issue when importing

(1) ShareShare
ReportReport
Posted on by Rafal Strozyk 7

Hello,

I'm trying to update my customized NAV 2015 from CU 7 to CU 10. I'm using Powershell cmdlets to prepare a file with all merged application objects. Unfortunately I'm not able to import my result file in NAV. Problem is caused by some design changes in the base objects area. For Example Table 370 Excel Buffer: in CU10 there is a new column "16 - Double Underline" which doesn't exist in CU 7. When I try to import my merged file I get an Error:

"Your program license does not allow you to create the Double Underline field in the Excel Buffer table."

Is there any workaround for this problem?

*This post is locked for comments

  • Suggested answer
    keoma Profile Picture
    keoma 32,675 on at
    RE: Application Objects Merge - License issue when importing

    first add the needed field in the existing table, then try again.

  • Suggested answer
    jcastro Profile Picture
    jcastro 2,245 on at
    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

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.

Helpful resources

Quick Links

Daivat Vartak – Community Spotlight

We are honored to recognize Daivat Vartak as our March 2025 Community…

Announcing Our 2025 Season 1 Super Users!

A new season of Super Users has arrived, and we are so grateful for the daily…

Kudos to the February Top 10 Community Stars!

Thanks for all your good work in the Community!

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 292,516 Super User 2025 Season 1

#2
Martin Dráb Profile Picture

Martin Dráb 231,430 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans