Skip to main content
Question

Troubleshooting customization project that works locally but does not work on cloud

  • May 11, 2026
  • 4 replies
  • 35 views

kevlynch
Jr Varsity II
Forum|alt.badge.img

I’m running into a strange issue where I have a customization project targeting PO screens with multiple purposes - some validations to prevent certain combinations of projects and subaccounts, and another to unlock certain fields like descriptions and such while the po is in pending approval status. 

When I publish this project on my local dev environment, all works great (no other customization projects installed). 

When I publish this exact same project on a client’s cloud environment, the validations work but the field unlocking under pending approval status does not. 

Both environment have exactly the same version and patch deployed (2026R1 Patch1). I’ve unpublished all other customizations and only published this project in both environments, and the same happens. 

In the dev environment, everything works as expected in both classic UI and modern UI. In the cloud environment it does not work in either. 

This customization used to work in 2025R1 on the cloud environment, but stopped working after an update to 2025R2, and still does not work under 2026R1. It always worked in the dev environment under all of these same versions.

Any idea where I can start looking to see what is causing this to not work in this specific environment?

Is there any way I can troubleshoot this on a cloud instance where I don’t have access to the server itself?

Thank you,

Kevin

4 replies

Dmitrii Naumov
Acumatica Moderator
Forum|alt.badge.img+7

Is there a modified workflow for the PO screen in the prod instance that is not in the dev instance?


kevlynch
Jr Varsity II
Forum|alt.badge.img
  • Author
  • Jr Varsity II
  • May 11, 2026

Is there a modified workflow for the PO screen in the prod instance that is not in the dev instance?

No, as mentioned, there were zero other customization projects published in either instance, and the exact same project zip file was imported in both places. I’m very stumped… 

The customization project does not include PO Workflow customization (when I tried that route to unlock fields it did not work so I’ve left it back to default).


Forum|alt.badge.img+8
  • Captain II
  • May 11, 2026

I would consider getting a backup of the tenant from the cloud and bring that into your dev environment. You could have a data configuration in production that’s different from your dev data that’s causing the code not to fire as expected.

You can also but trace statements to see if you can figure out why the code isn’t running as expected.


Naveen Boga
Captain II
Forum|alt.badge.img+20
  • Captain II
  • May 12, 2026

@kevlynch   Possible reasons:

1. Different Workflow from Dev to Cloud

Even same version can have:

  • Modified workflows
  • Snapshots
  • Imported packages
  • Tenant-level workflow changes

Also please check:

  • PO Preferences
  • Workflow customizations
  • Automation steps

I think the root cause is:

Pending Approval workflow state is forcing cache/view read-only in cloud tenant.