Skip to main content
Answer

Unpublishing Customization Project that impacts the instance in Multi-Tenants

  • March 11, 2025
  • 2 replies
  • 77 views

Hi Everyone

Could you please help me with a question regarding unpublishing customization that impacts the instance in a multi-tenant environment?

For example, we tested a customization that would impact the instance in a Test tenant. It works well. We publish it in Live tenant again. 

Due to another test we need to do in the test tenant, we unpublish this customization in test tenant, while the same customization project in Live remains published. 

My understanding is that some customizations impacts the instance, not just the tenant it is published in. Does it also in term have the same effect when we unpublish?  Removing the same customization in test tenant will impact live tenant and may cause errors. 

What would be the best practice when we want to test customisation in a multi-tenant environment?

Appreciate your insight and suggestions.

Thanks. 

 

Best answer by darylbowman

...Does it also in term have the same effect when we unpublish?  Removing the same customization in test tenant will impact live tenant and may cause errors...

In short, yes, although depending upon what is in the customization, this may vary.

 

What would be the best practice when we want to test customisation in a multi-tenant environment?

Best practice would be to test customizations in a sandbox instance instead.

2 replies

DipakNilkanth
Pro III
Forum|alt.badge.img+13

Hi ​@snzhang,


Have you checked below link? This will helps you to understand the impacts while publishing customization in multi tenant.
https://www.augforums.com/publishing-an-acumatica-customization-project/

Hope, it helps!


darylbowman
Captain II
Forum|alt.badge.img+15
  • Answer
  • March 11, 2025

...Does it also in term have the same effect when we unpublish?  Removing the same customization in test tenant will impact live tenant and may cause errors...

In short, yes, although depending upon what is in the customization, this may vary.

 

What would be the best practice when we want to test customisation in a multi-tenant environment?

Best practice would be to test customizations in a sandbox instance instead.