Publish to multiple instances confusion

Hello ​@stephenward03 ,

Really interesting question — this kind of use case definitely deserves a place in Acumatica ERP workflows.

I completely understand your concern about testing a customization package. Ideally, testing should happen in a dedicated test or sandbox instance. And even if you don’t have an additional license, you can always spin up a local instance with the SalesDemo data for that purpose.

However, it’s worth noting that you are allowed to test a package on your live environment, as long as it’s in a separate tenant and does not yet affect production users.

You also correctly pointed out that Acumatica uses a centralized DLL structure — there’s only one Bin folder for the whole site, and any DLLs you publish will be shared across all tenants.

In this case, the cleanest approach is to control feature activation via a simple checkbox.

Here’s how you can do it:

1. Add a checkbox on a relevant setup screen (it can be global or tenant-specific).

2. Enable this checkbox only for the tenants where you want the code to be active.

3. In your Graph or Cache Extensions, use the IsActive() method to check the checkbox's value.

4. For custom DACs or Graphs, you can use a check in the constructor, just like Acumatica does with graphs, which require some data from preferences.

If the feature isn't enabled, you can throw a PXSetupNotEnteredException like this:
 

throw new PXSetupNotEnteredException<YourDAC>("Your custom message here");

This pattern gives you full control over which tenants run your custom logic, even though the DLLs are shared.

Hi ​@harutyungevorgyan , thanks for your reply, the explanation is much appreciated. I have been thinking about adding the ability to switch features on/off within code and receiving this type of detail is very useful. 

However, the issue I’m struggling with is the with the ‘Publish to Multiple Tenants’ option. Is it possible to publish just one customisation to multiple tenants, or will Acumatica attempt to publish all customisations to all tenants?

I don’t want to publish all GIs, Reports, and Sitemaps for all customisation to other tenants, but I think this is what is going to happen.