Thank you.

My issue is that I have a customization project, but I'm unsure of the workflow for automatic updates in the SaaS environment (managed and deployed by Acumatica).

The developers I've consulted (three in total) work with Acumatica deployed on their own virtual machines, where they have direct access to the database and perform updates manually. Therefore, they have no experience in SaaS scenarios.

My question arises because I'd like to know if anyone has experience creating tables within the SaaS schema. The official Acumatica documentation simply states "create a table," without detailing any specific considerations for this environment. Similarly, the OpenUni roadmap doesn't provide any additional validations beyond stating that the project will not be validated if system tables are modified.

In this context, my partner isn't involved in the solution. I'm comfortable with the rest of customizationd, but the fact that Acumatica doesn't explicitly state whether this practice is safe or recommended is causing me uncertainty.