Subaccount restriction by "DEPARTEMNT" segment

Question

Hi All,I need assistance with below:For one our clients, with regards to subaccount restrictions, we have already set and implemented the GL Account to subaccount pairing restrictions (through the GL Account Access) screen, and that works fine.Our subaccounts string are designed in such manner that they include ‘department’ segment specifications (as can be seen below first screenshot for the ENGINEERING department). So, now we want to restrict further using the ‘department segment’ in the subaccount string, such that when a User selects a DEPARTEMNT in the Requests screen (see 2nd screenshot), then on the subaccount column in the detail line, only subaccounts with the ‘ENG’ (Engineering) should show for the user to choose among them (i.e., automatically filter the subaccounts on the line by the department selected at the top). Is it possible to configure such restriction groups without using the GL Account itself/ the users themselves, through standard acumatica configuration?I have been trying out to create a group (e.g., Engineering department below) then selecting the subaccount containing the ENG string, like how I did set up for those currently working restrictions (GL Account to Subaccount restriction). however the issue I have for this particular desired restriction, is that on the highlighted parameters below, I can’t seem to find the “department” field. Since the Department options isn’t included among these available options below, does that mean mean this type of restriction we keenly hope for, is not possible through ‘standard configuration’ ? To anyone who might have an idea, please assist.Thanks!

Rakshanda · Answer

Hi ​@wandile02,No, it is not possible to dynamically filter the subaccount list on a detail line based on a document header field (like Department) using standard Acumatica Restriction Groups.Why Standard Configuration Won't WorkRestriction Groups in Acumatica (such as GL Account Access or Subaccount Access) are designed for row-level security and master data validation. They link specific, static master entities (Users, Roles, Branches, or GL Accounts) to Subaccounts.The "Department" field on the Requests screen is a transactional header field, not a core security entity like a User or a Branch. Because of this, the Restriction Groups screens do not have a parameter to map a "Department" to a "Subaccount." The system doesn't natively support dynamic, on-the-fly UI filtering of detail lines based on non-entity header fields out of the box.How to Achieve This (Code Customization)To automatically filter the Subaccount selector on the detail line based on the Department selected in the header, you will need a minor code customization.We can createaGraph Extensionfor the Requests screen (RQRequestEntry) and modify the attributes on the Subaccount field in the document details cache (RQRequestLine). Specifically, they would append a[PXRestrictor]that compares the subaccount segment in the database to the header's currently selected Department field.Hope above works!!

Why Standard Configuration Won't Work

How to Achieve This (Code Customization)

Sign up

Social Login

Login to the community

Social Login