Skip to main content
Question

Multiple Screens enabled for Approval are not storing workgroup

  • October 1, 2026
  • 2 replies
  • 20 views

Hello Folks, 

I have ran into a somewhat challenging roadblock for creating Approval maps for multiple screens. 

These Screens Include: Change Orders(PM308000) and Purchase Requisitions (RQ302000), both screens seem to not save either the “Owner” or the “Workgroup” of that owner in the DAC SCHEMA making it impossible to create an approval map for these screens using one. 

For example: On the Change Order screen, there is no “Owner” field but acumatica should track a created by and therefore an owner field of that document. Also pulling in the Workgroup associated with that person. Acumatica is not doing any of this: 

 

We  can see on this screenshot that workgroup, owner are both empty but the created on field (Which i have blocked out for privacy) has a field inputted. 

Can someone explain why this is happening is this isolated to 26R1? 

2 replies

valentynbeznosiuk
Jr Varsity III
Forum|alt.badge.img+5

Hi ​@rpearson69 

Having Owner and Workgroup of the owner is not required to create approval maps, and it is mostly controlled by the screen logic. I don't see anything similar on the Change Orders, but Requisitions has a Creator field (RQRequisition.EmployeeID). I'd suggest thinking about alternative rules for your approval map, or about a small customization that adds the needed fields with data controlled through code.

In some complex cases, it can be beneficial to create a custom controller, for example a checkbox whose value changes based on certain rules, and use it in your approval map. This allows more complex logic and lets you use data from across the whole system, not just the current form, which removes the limitations.


KrunalDoshi
Semi-Pro III
Forum|alt.badge.img+7
  • Semi-Pro III
  • October 7, 2026

Hi ​@rpearson69,

CreatedByID and OwnerID are two different fields and has different aspects. CreatedByID comes from Acumatica's audit fields, whereas an approval-map Owner/Workgroup normally expects an actual owner/workgroup field available in the document DAC.

I would recommend populate OwnerID and WorkgroupID if it is not populated in any scenario, then using small customization on these screens. You can then use the same in Approval Map.

Hope this is helpful!