"There is already an object named 'XXXX_id' in the database"

(0) Share

Report

Posted on by Community Member

Hi all,

My first post is about a problem I have the last week.

When I try to install an extension in a CRONUS Sandbox in BC365 its everything ok. When I try to install in Production, I get this error.

1-I didnt modify any table or tableextension.

2- If I delete the cronus Sandbox and make another one with the same data of production environment I get the same error.

3- At this moment, in production I have the last Extension that was installed until I installed this.

4- I tried to install previous extension (with another version) but I get the same error.

5- I have tried too, to change the version APP.

Thanks.

8662.ErrorBusinessCentral.PNG

Categories:

Financial Management

I have the same question (0)

All responses (15)

Answers (1)

Stefano Demiliani 37,166 Most Valuable Professional on at

Like (0)

Report

It seems that you have an extension that has already published an object that you're trying to republish.

Is this error in production or in a sandbox? We need a more clear details on what have you done...

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi Stefano, thanks for your reply. At this moment I'm not able to develop anything.

I have this error in production and in the sandbox.

You dont have this problem in a sandbox CRONUS. But if you copy the data from production you have the same problem.

The table where we have this problem is the 50000. This table was created a long time ago...

I have renamed the table with another Id name and when I installed it I got the same error in the next table 50001.

Was this reply helpful? Yes No
Stefano Demiliani 37,166 Most Valuable Professional on at

Like (0)

Report

In the sandbox you can clean your environment from VS Code by using schemaupdatemode = "recreate" when deploying or by executing the following Powershell:

Sync-NavApp -Name <name of extension> -Version <Version of extension> -Tenant <Tenant name> -Mode Clean

In production, you're forced to deploy an object with a new name and ID and mark the old object as obsolete.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

I have tried to do the schema update mode = recreate but this did not fix anything I still get the same error.

How can I use the Sync-NavApp in the poweshell. I get an error when I try to use.

So, I will lose all the data in production, no?

Was this reply helpful? Yes No
Stefano Demiliani 37,166 Most Valuable Professional on at

Like (0)

Report

Have you import the modules for Powershell? Just as example:

import-module "C:\Program Files (x86)\Microsoft Dynamics NAV\110\RoleTailored Client\NavModelTools.ps1"

import-module "C:\Program Files\Microsoft Dynamics NAV\110\Service\NavAdminTool.ps1"

You need to use the correct folders for your on-premise BC sandbox.

In production no data loss and no Powershell.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

This is not in an on-premise BC sandbox. This is the Sandbox from the cloud.

Was this reply helpful? Yes No
Stefano Demiliani 37,166 Most Valuable Professional on at

Like (0)

Report

Ok more clear, so no Powershell. Try to deploy from VS Code with schemaupdatemode = recreate but using F6 instead of F5. Please then report the error message.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

This is the error message with option F6

Was this reply helpful? Yes No
Stefano Demiliani 37,166 Most Valuable Professional on at

Like (1)

Report

Ok so the object exists.

Have you changed the app ID from the first deployment? Can you check this?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Yes I have checked that before in my repo. The id is still the same....

I can't understand this error...

Was this reply helpful? Yes No