You’re offline. This is a read only version of the page.
I tried update NAV2018 using *.txt files first. But it requires some packages as for development. So i tried update NAV2018 with exported *.fob:
Share
ReportImport-Module "${env:ProgramFiles(x86)}\Microsoft Dynamics NAV\110\RoleTailored Client\NavModelTools.ps1" -WarningAction SilentlyContinue | Out-Null
Import-NAVApplicationObject -Path D:\work\namise.fob -DatabaseName NAV2018 -LogPath D:\work -SynchronizeSchemaChanges force -Confirm:$false
pause
But errors was shown:
and command was not processed succesfully. Is command Import-NAVApplicationObject ekvivalent for manual import proces? Can be used for *.fob too?
Open Microsoft Dynamics NAV Development Environment -> Click File -> Click Import -> Select .fob -> Message shown: The objects in D:\work\namise.fob could not be imported because there are objects already in the database with conflicting versions. Choose OK to open the Import Worksheet, or Cancel to stop the import. -> Click OK -> Click Replace All -> Click OK -> Click Synchronize Schema Force (Changed will be synchronized to the database table without validation. Data in table column that are affected by the changes will be deleted) -> Click Synchronizate changes to the corresponding tables in SQL Server Yes -> Use from select All table schema changes were synchronized with force -> Shown table where is Import completed (replaced XY) -> then restart NAV services -> Done
If is command Import-NAVApplicationObject equal to mentioned manual process. What does mean these errors? Are solvable?
Thank you a lot!
Kind regards
Lukas
Solution: Was missing parameter Overwrite for ImportAction.
Was missing parameter Overwrite for ImportAction.
Kind regards
Lukas
Hi Lukas,
Import-NAVApplicationObject MyAppSrc.txt -DatabaseName MyApp
This command imports all application objects in MyAppSrc.txt (text format ) into the MyApp database.
Please refer to this doc for more examples how to import multiple files from folder.
docs.microsoft.com/.../import-navapplicationobject
another suggestion export those objects to .txt and import using the mentioned command.
Hi, I have also got the same issue related to conflict using fob file. But if I use .txt file for same object having destructive changes Import-NAVApplicationObject works perfectly fine and synchronize schema forcefully. So, you use txt files if you want to import objects that can result in destructive changes.
Failed:
Success:
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
290,524
Super User 2024 Season 2
#2
Martin Dráb
228,493
Most Valuable Professional
#3
nmaenpaa
101,148
All responses (
Answers (