Hey everyone, i am currently working on Dynamics Nav to implement electronic invoicing for Italy Instances.
As the link states ( https://support.microsoft.com/en-us/help/4462650/mandatory-b2b-einvoicing-in-the-italian-version-of-microsoft-dynamics ) ,
there are only about 7-8 tables/ codeunits etc updated/changed , BUT when i run the FOB objects from the CU 22 (Dynamics NAV 2017) and i import them via Import Worksheet i get multiple merge conflicts in mulitple tables and code units that are not mentioned in the link above.(about 60 warnings)
Any ideas on how i can resolve the warnings? What would you do?
*This post is locked for comments
Version | Description |
---|---|
Original version | This is the baseline version of the solution that you want to upgrade, such as the original release of Microsoft Dynamics NAV 2016 or Microsoft Dynamics NAV 2017. |
Modified version | This is the version that you want to upgrade, such as a customer's Microsoft Dynamics NAV 2016 or Microsoft Dynamics NAV 2017 database with customizations and add-on solutions. |
Target version | This is the target of the merge process that you want to upgrade your application to, such as the standard version of the Microsoft Dynamics NAV 2018 database. |
for more details go through below link:
https://docs.microsoft.com/en-us/dynamics-nav/upgrading-the-application-code
Thanks for the reply , im still stuck on what should i use on OriginalPath... In target i use my current database with the customizations & in the modified i use the Cumulative update no.22 ,
What i use in original please?
Go ahead, below is command.
I suggest you, use power Shell ISE and before start merging first read carefully article and then go.
Merge-NAVApplicationObject -OriginalPath .\ORIGINAL -TargetPath .\TARGET -ModifiedPath .\MODIFIED -ResultPath .\RESULT
Hey again, after lot of research i have found that i need 3 text files for migration with Nav Development Shell.
Original File(Demo Databse) , Modified File( My datbase) and the CU Update File.. ALL files are objects in txt
Then i will use merge-NAVAppication command..
What do you believe about this solution , Binesh?
Thanks
Yes i do have a text version of the fob i want to import but i'm using the Import Worksheet
for merging i suggest you,first export or convert your fob file into text, because for merging process u need text file.
I have modified database. If i import text file,all tha changes will be overwritten
Hello Dimitri,
First export the objects in text format, you can also convert fob file to text using powershell.
follow the below links for reference:
https://docs.microsoft.com/en-us/dynamics-nav/how-to--merge-application-changes
if still you have conflicts then use compare tools like beyond compare and manually merge the changes.
Sohail Ahmed
2
mmv
2
Amol Salvi
2