Hi experts,
I used PowerSheel Cmdlet to update my Application code. when i try to import All-merged.txt file in my database some objects can't be imported i get this error : you are not allowed to create ......
but when i import a that object as a FOB it works fine !!
Nb : Knowing that i use my developer licence,
*This post is locked for comments
Did you update your partner license after September 9th?
Try with new license.
markbrummel.wordpress.com/.../grab-your-power-license-create-table-1
For Importing text file object you need to have developer license .Kindly check your license
You cannot you Join-NAVApplicationObjectFiles cmdlet on .fob the source and destination need to be .txt files. Anyhow it looks like you have used powershell cmdlets to merge the application now you have the Result .txt file which you want to import correct ? since the target object has new objects or object fields which are not in the custom range you cannot just import the Result.txt file, since our license will not permit to create those objects.
What you need to do is, take the target .fob file and import it and using the import worksheet, in the import worksheet filter it for type table then except for Action create all other change entries Action change to Merge: Existing <- New , this will make sure to add the new fields in the tables or create new tables. Once this is done you can use your Result.txt file to import.
Hi Medo,
The error you get is most likely due to standard tables containing new standard fields. That applies to system tables (those in range 2000000000..) that the structure may change when you apply new Cumulative Updates.
"But when i export one of those object from Standard 2016 as Fob object i can import it in my database with same licence" ==> A fob file contains compiled objects that you can import to NAV even without developer license. This is why you can export/import fobs from standard database.
So, in order to merge your code; you'll need to have three databases/objects files:
Your goal is to create the "New Custom" objects/database. For that, I suggest you to follow the steps described in this video in order to understand the process of merging NAV objects using Powershell.
I hope this answer will help you.
Hi luc,
But when i export one of those object from Standard 2016 as Fob object i can import it in my database with same licence.
What i should do right now :
delete those objects form Txt file and import them later. or what i should do
Best regards
Eventhough you give the file the extension .fob internally it is a .txt file. Importing this pseude .fob file will thus give an import erro on object outside of your license range - typically these are new standard MS objects and fields.
Hi Suresh,
i used this command Join-NAVApplicationObject –Source C:\Upgrade\RESULT\*.txt -Destination C:\Upgrade\all-merged.Fob
however the problem persists !
Best regards
You cannot use text, because your license will not permit to create objects or object fields which are not in the custom range. You need to use .fob.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
André Arnaud de Cal... 291,240 Super User 2024 Season 2
Martin Dráb 230,149 Most Valuable Professional
nmaenpaa 101,156