Deletes objects from the specified Microsoft Dynamics NAV database.

finsql.exe command=deleteobjects, [servername=<server>,] [database=<database>,] [filter=<filter>,] [logfile=<path and filename>,] [username=<user name>,] [password=<password>,] [ntauthentication=<yes|no|0|1>,] [synchronizeschemachanges=<yes|no|force>,] [navservername=<server name>,] [navserverinstance=<instance>,] [navservermanagementport=<port>,] [tenant=<tenant ID>]

Parameters

servername

The name of the database server that hosts the Microsoft Dynamics NAV database that contains the objects that you want to delete. The format of this parameter is <computername>\<database server instance>.

If you do not specify both the servername parameter and the database parameter, then the database server and database that are stored in the fin.zup file are used.

Note
When you first specify a database server and database to open, either from a command at a command prompt or from a client, the database server and database are stored in the fin.zup file. By default, the fin.zup file is located at C:\users\<user name>\AppData\Roaming\.

If you do not specify the servername parameter but you do specify the database parameter, then the Open Database window opens so that you can specify the database server name.

Tip
To view the name of the server on which the current database is stored, on the File menu, choose Database, and then choose Information. Use the value of the Database Server field for the servername parameter.

database

The name of the Microsoft Dynamics NAV database in which the objects that you want to delete are stored.

If you do not specify both the servername parameter and the database parameter, then the database server and database that are stored in the fin.zup file are used.

Note
When you first specify a database server and database to open, either from a command at a command prompt or from a client, the database server and database are stored in the fin.zup file. By default, the fin.zup file is located at C:\users\<user name>\AppData\Roaming\.

If you do not specify the database parameter but you do specify the servername parameter, then the Open Database window opens so that you can specify the database name.

Tip
To view the name of the current database, on the File menu, choose Database, and then choose Information. Use the value of the Database Name field for the database parameter.

logfile

The path and file name for the file that contains error messages that result from the command. If there are no errors, then a log file is not created.

By default, the file is named naverrorlog.txt and is located in the same location as finsql.exe.

The navcommandresult.txt file, which contains information about the success or failure of the command, is created in the folder that is specified by the logfile parameter.

When you run finsql.exe with a command, the previous log file and result file are deleted.

Note
If User Access Control (UAC) is turned on and you do not specify to run the Command Prompt window as Administrator, then the Command Prompt window runs as a standard user. In this case, if you do not specify the logfile parameter, then the command fails because the standard user cannot write to the default location of the log file.

filter

A filter on the Object table. Use the filter parameter to specify which objects to delete. Use a semicolon to separate multiple filters. The only operator that you can use in the filter is '='. The following table shows the fields in the Object table on which you can filter.

Object table field Values Example

Type

Table, Codeunit, Page, Report, XMLport, Query

Type=Table|Page

ID

Integer or range of integers

ID=50000..50500

Name

Any valid object name

"Name=Cost Entry"

Modified

yes, no, 1, 0

Modified=yes

Compiled

yes, no, 1, 0

Compiled=0

Date

Date, in the numeric format determined by your regional settings

Date=8/11/2016

Time

Time, in the numeric format determined by your regional settings

Time=12:00:00

Version List

Any valid version

Version List=NAVW17.00

Caption

Any valid caption

Caption=Company Information

Locked

Yes, no, 1, 0

Locked=1

Locked By

Domain\username

"Locked By=CRONUS\viktor"

If you do not specify a filter, then all objects in the Object table are deleted.

username

The user name to use to authenticate to the database. The user name must exist in the database. If you do not specify a user name and password, then the command uses the Windows user name and password of the current user to authenticate to the database.

Note
If User Access Control (UAC) is turned on and you do not specify to run the Command Prompt window as Administrator, then the Command Prompt window runs as a standard user. In this case, if you do not specify the username parameter and the current Windows user is an Administrator, then the command is run as the standard user.

If you specify the username parameter, then you must also specify the password parameter and the ntauthentication parameter must be no.

For more information about database users and permissions, see Setting Database Owner and Security Administration Permissions.

password

The password to use with the username parameter to authenticate to the database. If you do not specify a user name and password, then the command uses the Windows user name and password of the current user to authenticate to the database.

ntauthentication

Specifies if you want to use NT authentication. The possible values are yes, no, 1, or 0. If you specify the username and password parameters, then you must specify ntauthentication=no or ntauthentication=0.

synchronizeschemachanges

Specifies how to synchronize table definition changes in the business (tenant) database in SQL Server. The following table describes the available options.

Option Description

yes

Before applying changes to the business data table, Microsoft Dynamics NAV Server validates the changed table definition to check for destructive changes to the table. This includes changes that require that data is deleted in the fields of the business data table which are affected by the changes before the changes can be applied.

  • If there are no destructive changes to the table, then the schema changes are applied to the business data table immediately.
  • If there are destructive changes, Microsoft Dynamics NAV Server checks that there are table synchronization instructions in an upgrade codeunit. If there are instructions, then the schema changes are applied to the business database table according to the instructions. If there are no instructions, then an error message appears. The table definition changes are not saved and the schema changes are not applied.

no

Table definition changes are saved and compiled in the application but the changes are not validated or applied to the business data table. You synchronize the table schema later by doing one of the following:

  • Save or compile the table from Object Designer in development environment and choose either the Now - with validation or Force synchronization option.
  • Use the Sync. Schema for All Tables option on the Tools menu.
  • Run the Sync-NAVTenant cmdlet from the Microsoft Dynamics NAV 2017 Administration Shell.

force

Table definition changes are applied to the business data table schema without validation. For destructive changes, data in columns of the business data table that are affected by changes will be deleted.

This option ignores any table synchronization instructions for the table in upgrade codeunits.

For more information about table schema synchronization, see Synchronizing Table Schemas.

navservername

Specifies the name of the server that hosts the Microsoft Dynamics NAV Server instance, such as MyServer.

Use this parameter only when you are deleting table objects and the validatetablechanges is set to no.

navserverinstance

Specifies the Microsoft Dynamics NAV Server instance that is being used, such as DynamicsNAV90.

Use this parameter only when you are deleting table objects and the validatetablechanges is set to no.

navservermanagementport

Specifies the port on the Microsoft Dynamics NAV Server server that the Microsoft Dynamics NAV Windows PowerShell cmdlets access, such as 7045.

Use this parameter only when you are deleting table objects and the validatetablechanges is set to no.

tenant

Specifies the ID of the tenant that is accessed when you run objects from the development environment. If your solution is not set up to deploy in a multitenant deployment architecture, then leave the parameter empty.

Use this parameter only when you are deleting table objects and the validatetablechanges is set to no.

Remarks

When you run the command, objects are deleted without a warning or confirmation prompt.

Example

This example shows how to run the DeleteObjects command to delete all tables and codeunits that have an ID that is greater than or equal to 500 and less than or equal to 1000.

 Copy Code
finsql.exe command=deleteobjects, servername=TestComputer01\NAVDEMO, database="Demo Database NAV (9-0)", filter="Type=Table|Codeunit;ID=500..1000"

See Also