Microsoft Dynamics NAV (Archived)

Import-NAVApplicationObject issue when using Application merge utility

(0) Share

Report

Posted on by aavio

895

Hi all,

Please help to clarify the following issue when using application merge utility.

In case if cumulative update have a new additional std field, how is it supposed to import to the new custom version.

Merge utility correctly compared and merged the new std field, but when i import the merged text file, it hit the usual error "Your program license does not allow you to create ... ".

Sample - base version is 2015 RTM, new base version is NAV 2015 cumulative update 9. In CU9, table 5 there is a new std field, ID 16.

Do we need to first import the table object as fob with merge action 'Merge: Existing<-New'?

*This post is locked for comments

All responses (2)

Answers (1)

aavio 895 on at

Like (0)

Report

RE: Import-NAVApplicationObject issue when using Application merge utility

Thanks for clarifying.

In that case it makes additional step to check those std fields and import one by one, as we dont know how many such new fields added.

would prefer AMU to handle it using merge action parameters as well.
Verified answer

Suresh Kulla 44,614 on at

Like (0)

Report

RE: Import-NAVApplicationObject issue when using Application merge utility

Yes you need to import that as .fob with Merge : Existing <- New so that all fields will be imported then you can import .txt.

Since those are standard field number we don't have license or permission to create those fields.