Skip to main content

How SQL Database / Table & Field Name Changed When we Use Some Special Character in NAV?

Hi All,

One of my NAV Friend while working on SSRS Reports asked a Question. Below is the Query is his words?
"Hey Saurav - When I trying to access table Sales Prepayment % or Field Prepayment % or using a database Named as Demo Database NAV (7-0) I get a different name is SQL instead of Navision. Why there is a change? Which all character get changed? Where I can find this change Character List?" 
So those who Know this, I guess what is below is nothing new for you, but those who still are curious about it should Read Ahead...

So lets see Which all Character Get Changed?

IN NAV 2009 ==> ."\/'
IN NAV 2013 & 2013 R2 ==> ."\/'%][

Can i Add more to This List?

YES

Where is can be seen in NAV?

1. Navigate to File - Database - Alter.
2. Open Integration Tab.
3. The Above Special Character List is Stored in Field called Convert Identifier Field as shown below.



In Which Table the character list is Stored & How can we get it?

You cannot access the List (Field Content) in Navision, but from SQL you can get it.
The Character list is stored in Table $ndo$dbproperty Which can be accessed by SQL Server Management Studio as Shown below.


** Do not change the content of this table until and unless you are sure what you are doing.

What Happens to the Special Character which are listed here?

This setting allows you to select the invalid characters in the names of all the SQL Server objects (tables, columns, constraints) in the database that you want to map to the underscore character.

Convert Identifier field contains a list of the characters that are converted to underscores. You can modify this list.

How can I Append ?

Append the any other Special Character in Field and Click OK. When the conversion is completed, the database must be closed and reopened before you can use the new identifiers.

Hope the information help to my readers. Do let me know your feedback as comments.

"These postings are provided "AS IS" with no warranties and confer no rights. You assume all risk for your use."

Regards,
Saurav Dhyani
www.sauravdhyani.com

Comments

Popular posts from this blog

BC 21 and Higher - PowerShell Cmdlet (Replacement of Business Central Administration).

Hi Readers, As discussed in last article about deprecating of Business Central Administration, there are few common actions that we use in administration till Business Central 20. For our on-prem customers, we will still require doing activities. As Microsoft suggest we need to start using PowerShell cmdlet.    Let's see how to do those via PowerShell, or Administration Shell. I will be keep adding commands as you comment to this article.

Send Mail with Attachment From Navision.

Hi all, We have seen how to save a report into PDF and how to send mail to a customer. Let's link these two post in one i.e. Mailing statement to a customer into PDF Format. This article is part of the Series. Please Refer  Table of Content here . If you have the old objects set let me brief you what I will be changing - 

MSDYN365BC - Data Upgrade To Microsoft Dynamics 365 Business Central on premises.

Hi Readers, We have already talked about the number of steps for upgrading to Business Central on Premises from different NAV versions. After that article, I received multiple requests for an article which list down steps for Data Migration. In this article, we will discuss steps of data migration to MSDYN365BC (on-Prem) from NAV 2017. For this article, I am considering a Cronus Demo Database without any customization. For an actual upgrade project, we will have to complete object merge using compare and Merge process. After the Merge Process, the next step is data migration. Let's discuss those steps. Direct Upgrade to Microsoft Dynamics 365 Business Central (on-Prem) is from following versions - 1. NAV 2015. 2. NAV 2016. 3. NAV 2017. 4. NAV 2018.