How to give user with multiple roles access to Generate on Demand Statement

Hi There,

What I’ve found is generally, if a user has multiple overlapping roles (this is from experience, as I don’t think I’ve ever seen this in the documentation), the most permissive access will prevail unless specific restrictions have been made to nested items within the form.  I have seen scenarios where I’ve revoked access to specific buttons for one role, and the rest of the roles have that button as “inherited” and then if the user has any other roles they still cannot access the button (see the last example here)

https://help.acumatica.com/(W(8))/Help?ScreenId=ShowWiki&pageid=5b4ebfa6-7bb0-43be-a191-83843e9f808d 

With the generate on demand statement, there is also a bit of a “funny” workflow in that you have to press the “Generate on Demand” button to generate it, but nothing actually pops-up on the screen.  Then you have to press the “Print Statement” button to actually get the statement to print (or use the Print Statement screen to print it from there).
 

The calculation of restrictions is here:  https://help.acumatica.com/(W(1))/Wiki/ShowWiki.aspx?pageid=5b4ebfa6-7bb0-43be-a191-83843e9f808d

I found a path that gave a user rights to Generate On Demand.  In Access Rights by Screen, give Edit rights to all related the roles you want to have it on Receivables>Customers.  Anything less than Edit on that particular level will not let the user see it.   I didn’t necessarily want the users to be able to Edit customers, but I don’t see where I have a choice.  Giving right to just the Generate On Demand object doesn’t get the job done.

I tried all of the suggestions in this post and another post and the only thing I got to work was giving edit rights at this higher level.  Generate On Demand is nested a couple of layers under Receivables>Customers and it became an inherited right, which I left as is.