Managing Customizations - Everything Else https://www.augforums.com/forums/everything-else/managing-customizations/ Acumatica User Group Forums en-US Wed, 14 Oct 2026 11:49:47 +0000 wpForo 60 RE: Managing Customizations https://www.augforums.com/forums/everything-else/managing-customizations/#post-3705 Sun, 24 Feb 2019 21:42:26 +0000 Tim, just to clarify, when i was referring to database changes it was DML changes and not DDL changes. In other words, records in a table and not table structural changes. 

I agree that Acumatica isn't true Multi-Tenant. 

I still remember when I tried to copy some GIs to a new Tenant and in the process managed to remove all of our Partner made customisations from our main Tenant. That's why i don't use publish any more and manage it all manually. 

]]> Everything Else Royce Lithgo https://www.augforums.com/forums/everything-else/managing-customizations/#post-3705 RE: Managing Customizations https://www.augforums.com/forums/everything-else/managing-customizations/#post-3678 Sat, 23 Feb 2019 05:10:51 +0000 Royce, I agree with your database level changes comment, but some database changes (like adding a field to a table) affect all Tenants. In general I've experienced that front-end changes affect all Tenants, but I've seen some specific front-end customizations that can vary by Tenant. It's so confusing though that I personally prefer to have one set of Customizations and apply them to all Tenants. That's definitely the safest thing to do. And I totally agree with you, PUBLISH is broken and needs an overhaul. Acumatica isn't TRUELY multi-tenant in my opinion. If it was, then Tenants wouldn't be able to impact other Tenants (like publishing in one Tenant removing customizations in another Tenant).

Sorry for the confusion between Tenants/Companies. I was following the lead in the first post to use the "2017 R2 and prior" terminology. I modified my post above to hopefully be more clear. I also added a new post with a graphic explaining the difference between Instance/Tenant/Company/Branch in 2017 R2 and prior vs. 2018 R1 and later:

https://www.augforums.com/augforums/everything-else/instance-vs-tenant-vs-company-vs-branch/

]]> Everything Else Tim Rodman https://www.augforums.com/forums/everything-else/managing-customizations/#post-3678 RE: Managing Customizations https://www.augforums.com/forums/everything-else/managing-customizations/#post-3601 Thu, 14 Feb 2019 03:53:41 +0000
Posted by: Jerwin Alimuin

I think the customization really apply to all tenants, even you have created customization in Tenant 1, once you published it will be automatically applied to all remaining tenants.

That's only true for Site level customisations - database level changes (eg. Site Map) will not be published to all Tenants through a single publish (to one Tenant).

]]> Everything Else Royce Lithgo https://www.augforums.com/forums/everything-else/managing-customizations/#post-3601 RE: Managing Customizations https://www.augforums.com/forums/everything-else/managing-customizations/#post-3600 Thu, 14 Feb 2019 03:04:20 +0000 For the automatically unpublishing issue when publishing, you must publish inside the customization window. Then the other customization will remain published.

]]> Everything Else Jerwin Alimuin https://www.augforums.com/forums/everything-else/managing-customizations/#post-3600 RE: Managing Customizations https://www.augforums.com/forums/everything-else/managing-customizations/#post-3599 Thu, 14 Feb 2019 02:58:40 +0000 I think the customization really apply to all tenants, even you have created customization in Tenant 1, once you published it will be automatically applied to all remaining tenants.

]]> Everything Else Jerwin Alimuin https://www.augforums.com/forums/everything-else/managing-customizations/#post-3599 RE: Managing Customizations https://www.augforums.com/forums/everything-else/managing-customizations/#post-3577 Mon, 11 Feb 2019 14:57:03 +0000 We are running 2017 R2. I did verify with support that it is not possible to Publish separately from inside Acumatica.

]]> Everything Else Geremy Partridge https://www.augforums.com/forums/everything-else/managing-customizations/#post-3577 RE: Managing Customizations https://www.augforums.com/forums/everything-else/managing-customizations/#post-3574 Sun, 10 Feb 2019 22:42:19 +0000 @shawn-slavin - This was for version 6.1.  We have since migrated them to 2018R1. The problem still exists, if they are a tenant in the installation and you customize the screens, then it applies to all tenants. It makes sense it would because they all share the same site. Customizing the database though will make it specific to the tenant.

]]> Everything Else Mindover https://www.augforums.com/forums/everything-else/managing-customizations/#post-3574 RE: Managing Customizations https://www.augforums.com/forums/everything-else/managing-customizations/#post-3573 Sun, 10 Feb 2019 21:06:08 +0000 Tim, I think you might have missed the issue asked here about customisations applying to one Tenant but not the others. If these customisations are Front-End, then my understanding is that it's not possible. Once you publish Front-End (eg. Page) customisations to ANY Tenant, they will apply to ALL Tenants because Tenants are a database level concept whereas Pages are an Instance level concept.

If you ask me, Publish is broken and needs an overhaul. I've been caught out by its traps before. 

]]> Everything Else Royce Lithgo https://www.augforums.com/forums/everything-else/managing-customizations/#post-3573 RE: Managing Customizations https://www.augforums.com/forums/everything-else/managing-customizations/#post-3565 Fri, 08 Feb 2019 22:18:41 +0000 I also think it is important to be sure we are all using the same terminology. What version are you running @Mindover? If you are using 2017 R2 or earlier, then you should be able to publish Front-end customization by company as Tim lays out in his earlier comment.

If you are using 2018 R1 or later, you should be able to publish front-end customizations by tenant. 

Starting in 2018 R1, what was called company was renamed to tenant and a new middle layer of organizational structure called 'Company' was introduced. This uses the Branches table to manage this new construct. 

All this to say, I am not aware of a way to have different customs by company in 2018 R1 and later within the same tenant.

]]> Everything Else Shawn P Slavin https://www.augforums.com/forums/everything-else/managing-customizations/#post-3565 RE: Managing Customizations https://www.augforums.com/forums/everything-else/managing-customizations/#post-3563 Fri, 08 Feb 2019 15:26:20 +0000 Hi Everyone.

 I am having the same issue. 

We have 2 separate companies but they both need different customizations applied. I am having a hard time trying to figure out where to publish them from. We had an incident recently where somebody published the customizations in Company 2 and it removed all of the customizations from Company 1. 

I don't want the customizations for Company 1 in Company 2 and vice versa. I need to keep them isolated. Is there a way to do this?

Thanks.

]]> Everything Else Geremy Partridge https://www.augforums.com/forums/everything-else/managing-customizations/#post-3563