Skip to main content

NAV 2013 R2 - Multi- Tenancy - Tables with Data Comman to All Companies.

Hi all,

I found one more issue after applying Multi - Tenancy to my database.

Here is the problem -

When i try to create a table with DataPerCompany Property Set to NO, Developer Environment give an error message saying

"There are multiple tenants mounted on the server. Validating table layout changes to protect against data-loss is only supported with a single tenant mounted on the server."





Way Around -

* It's Just a way around / finding but please validate from Microsoft before applying same on customer database.

1. Save the Table with DataPerCompany as Yes.



2. Navigate to Tools - options and change the value for property "Prevent data loss from table changes" to NO and click Ok.



3. Design table and change the Value of Property to DataPerCompany to NO, and save the table.


4. Let's Open SQL Server and check the Table in Application database and tenant database. If you see you will not find new table created in any of the database.

5. What we need to do is -

a) you need to reset the property "Prevent data loss from table changes" to YES under tools - Options.

b) You need to restart the Service tier.

Now if you see in SQL Server you will find the table in every tenant just like the company table.

Regards,
Saurav Dhyani
saurav-nav.blogspot.in

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.