Manage objects in Microsoft Dynamics NAV 2013 R2 Dev Environment from command prompt
RUN-> cmd
C:\Program Files (x86)\Microsoft Dynamics NAV\71\RoleTailored Client>
To Export Objects:
In fob file type
C:\Program Files (x86)\Microsoft Dynamics NAV\71\RoleTailored Client>finsql command=exportobjects, file=C:\vendor_obj.fob, servername=MITSYS, database=NAVDEMO71, filter="Type=Table;ID=23"
In text format file type
C:\Program Files (x86)\Microsoft Dynamics NAV\71\RoleTailored Client>finsql command=exportobjects, file=C:\vendor_obj.txt, servername=MITSYS, database=NAVDEMO71, filter="Type=Table;ID=23"
To Import Objects:
C:\Program Files (x86)\Microsoft Dynamics NAV\71\RoleTailored Client>finsql command=importobjects, file=C:\vendor_obj.txt, servername=MITSYS, database=NAVDEMO71
To Compile Objects:
C:\Program Files (x86)\Microsoft Dynamics NAV\71\RoleTailored Client>finsql command=compileobjects, file=C:\vendor_obj.txt, servername=MITSYS, database=NAVDEMO71, filter="Type=Table;ID=23"
To Design Objects:
C:\Program Files (x86)\Microsoft Dynamics NAV\71\RoleTailored Client>finsql designobject=Table 23
Filters:
You can use any of column name in object designer and any of commands like exportobjects, importobjects, compileobjects etc.
Examples:
1. C:\Program Files (x86)\Microsoft Dynamics NAV\71\RoleTailored Client>
finsql command=exportobjects, file=C:\objects.txt, servername=MITSYS,
database=NAVDEMO71, filter="Type=Table;Name=C*"
2. C:\Program Files (x86)\Microsoft Dynamics NAV\71\RoleTailored Client>finsql
command=exportobjects, file=C:\objects.txt,
servername=MITSYS, database=NAVDEMO71, filter="Name=C*"
3. C:\Program Files (x86)\Microsoft Dynamics NAV\71\RoleTailored Client>finsql
command=exportobjects, file=C:\objects.txt, servername=MITSYS, database=NAVDEMO71, filter="Date=10/01/13"
Import object in Multi tenant environment
C:\Program Files (x86)\Microsoft Dynamics NAV\71\RoleTailored Client>finsql command=importobjects,
file=C:\objects.txt, servername=MITSYS, database=DemoNAVAPP, importaction=overwrite,
validatetablechanges=yes/no navservername=localhost, navserverinstance=DynamicsNAV71,
navservermanagementport=7045, tenant=t1
Friday, January 31, 2014
NAV Errors and solutions
1. Error Message
---------------------------
You cannot start Microsoft Dynamics NAV Classic because you do not have the VIEW SERVER STATE permission on SQL Server. Contact your system administrator.
Solution
USE [master]
GO
GRANT VIEW SERVER STATE TO PUBLIC
GO
-------------
2. Error message
The page contains a control add-in that is not permitted. Contact System Administrator
Solution:
NAV 2009 Sp1 comes with addin by default.
Run table from object designer named. Client Add-in 2000000069.
In the table write the following data.
Control Add-in Name: Microsoft.Dynamics.NAV.MicrosoftDynamicsOnlineConnectControl
Public Key Token: 31bf3856ad364e35
Description: Microsoft Dynamics Online Connect control add-in
---------------------------
You cannot start Microsoft Dynamics NAV Classic because you do not have the VIEW SERVER STATE permission on SQL Server. Contact your system administrator.
Solution
USE [master]
GO
GRANT VIEW SERVER STATE TO PUBLIC
GO
-------------
2. Error message
The page contains a control add-in that is not permitted. Contact System Administrator
Solution:
NAV 2009 Sp1 comes with addin by default.
Run table from object designer named. Client Add-in 2000000069.
In the table write the following data.
Control Add-in Name: Microsoft.Dynamics.NAV.MicrosoftDynamicsOnlineConnectControl
Public Key Token: 31bf3856ad364e35
Description: Microsoft Dynamics Online Connect control add-in
Subscribe to:
Posts (Atom)