+1
If a customer has a Live and Test tenant what are the ramifications of publishing a customization in Test for testing and not in Live ?
Is there any documentation that says you can publish in one tenant and not the other ?
Best answer by kpopova
View original
+6
good luck!!
Here is documentation about publication in multiple tenants: https://help.acumatica.com/(W(34))/Help?ScreenId=ShowWiki&pageid=d1afb862-c7fe-4257-9978-886c7b05746a
+11
good luck!!
This is unfortunately NOT the case (in my experience).
Any database changes will affect all tenants of that instance, which isn’t necessarily a problem unless changes are made that you want to undo. That gets messy.
Also, during publish, all tenants will be affected, which means users will lose their unsaved work when they are forced to reload their session. This can cause frustration on their part.
It is safest to test customizations in a separate instance.
Customizations affect every Tenant contained within the URL regardless of which Tenant it is published to. To test code, a separate Sandbox is required with a different URL.
I thought at one point Acumatica was working on overcoming this, but I haven’t heard anything lately.
-John
+12
Hi
only option we have is to publish the packages in both the tenant and completed the work in non-business hours.
Please find the below article on package publishing details
We faced the same issue.When we asked the solution we advised to use conditions inside every event handlers and DAC extensions.
if(PX.Data.Update.PXInstanceHelper.CurrentCompany==’your tenant id’){
//write your logic
}
After testing is okey you need to remove this part and publish to prod tenant.
But,As I assumed it’s not a permanent solution and it is wasting the time.
I thin Acumatica needs to work on it.
+11
We faced the same issue.When we asked the solution we advised to use conditions inside every event handlers and DAC extensions.
if(PX.Data.Update.PXInstanceHelper.CurrentCompany==’your tenant id’){
//write your logic
}
After testing is okey you need to remove this part and publish to prod tenant.
But,As I assumed it’s not a permanent solution and it is wasting the time.
I thin Acumatica needs to work on it.
This pairs well with the IsActive property that Acuminator makes you add to every graph or cache extension. However, this doesn't alter how it changes shared resources. It only changes whether it's active or not in the tenants.
Hi
What is your suggestion to overcome this issue. Is creating a separate tenant and do the all the customization in here and published to actual one at once?
+11
No, my recommendation is to use a separate instance entirely. Acumatica is free to download and install. There's really very few downsides.
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
