GI Parameters Data visibility

​@Godawela 

If the user needs to view information from A/B/C on one screen, I would recommend evaluating a dedicated custom inquiry with this design:

1. Keep the user’s normal branch access restricted to A.
2. Create a separate role that authorizes access to the special inquiry. Do not configure this role as the Access Role for Branch B or C.
3. Implement the inquiry’s data retrieval so authorized users can see only the approved data from A/B/C within that inquiry.
4. Keep access to the underlying transaction screens subject to the user’s normal permissions. Seeing a B/C record in the inquiry should not automatically allow opening or editing it elsewhere.

This is a proposed customization design; the exact implementation depends on the screen, source tables, and Acumatica version

Hi ​@Godawela ,

In reports you have an option to use AccessInfo.BranchID, but in generic inquiries unfortunately such option is not available. You also can’t join this table as AccessInfor is virtual table that does not exist in database.

However there is a workaround – we create a parameter in GI, that will get a default value from any branch field in Acumatica that has a default value from current branch and than use this filter for filtering. based on your requirement create GI by adding Branch as parameter
As below-

1. We need to create a parameter that will store a current Branch.
   1. This parameter should not be visible for user, so he can’t change it. To do this we can set Hidden flag to False. Hidden flag column is hidden by default so please check columns configuration.
   2. Default value can be taken from any of the the existing field where this default is used. Just for example – if you create a new Invoice (or order or payment, etc) the Branch field will be automatically populated by Acumatica. This is defaulting behavior that we can reuse in GI. SO if we set Schema Field to the field that has a default to current branch, the same value will appear in our GI. Please note that it is not necessary to join table in SQL to use it as a Schema Field. You can just mention it.
   3. It also makes sense to make this field as required to not provide any data if there is no current branch.

   

2. Now we need to apply a filtering condition by this parameter:
   

That is it! Now you GI filters out all branches that is not current!

Hope above helps!!