Skip to main content
Question

Customization Projects clarification

  • November 25, 2024
  • 4 replies
  • 79 views

Forum|alt.badge.img

Hello all,

I have been working with customization projects for some time, and I can’t quite seem to figure out why sometimes they publish to the database, sometimes to one tenant, and sometimes to multiple tenants? It seems to be almost random, and I can’t seem to find a pattern.

 

I understand there is the “Publish to multiple tenants” option; however, when I do this in Test and publish to both Production and Test tenants, the projects sometimes don’t publish into the Production. The times they do publish into Production, they still seem to “live” in the Test Customization Projects screen and don’t update the customization projects in production. E.g.- I make edits to a side panel in Test, publish to Test and Prod. I go into the customization in Prod and the changes are not in the project; however, the side panel displays in Prod Acumatica where it needs to be.

I have looked over the community, but I can’t seem figure out the best practice and explanation with these projects!

Thanks,

-RJ

4 replies

Nilkanth Dipak
Semi-Pro I
Forum|alt.badge.img+10

Forum|alt.badge.img
  • Author
  • Semi-Pro I
  • 30 replies
  • November 25, 2024

@Dipak Nilkanth 

Thanks for the response. I have checked these pages before, but it still is unclear to me. It states ”the selected tenants share customization data that is specific to the opened tenant and stored exclusively in the database; however, it seems they only store in one tenant. 

 

If the project from Test gets published into production and test, and not stored in production, I worry someone in the future will edit the project from Production and re-publish, and the changes from Test will not be in production anymore. 


darylbowman
Captain II
Forum|alt.badge.img+13

As far as I know, code customizations are never tenant-specific. However, the documentation is unclear to me also. I only store customizations in the first tenant and only ever publish from there.


Forum|alt.badge.img+3
  • Jr Varsity I
  • 62 replies
  • November 26, 2024

In my experience, customizations with DLLs that restart Acumatica are published to all tenants (the DLL affects the entire instance). Customization that consist of inline code or workflows need to be published to all tenants to work properly.

Obviously, database update affect the one underlying database. However, the DAC layers will follow the above.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings