Great post John!

What version and update of Sage 300 CRE are you currently using? The version will reference 9.8 or 13.1 in your Help, About in the software. (example 13.1 Rev 7 Acc Update 6)

This will help the other users compare their set up to yours! Thanks!

We are using 13.1 Rev 7 Update 9

Hi John,

One thought I had involves a series of formulas to mimic the Role setup that Sage Security Administration uses.

You could setup a formula If (Project Manager = Group 1, If (Operator = A or Operator = B or Operator = C ... , YES)) (The syntax will need to be changed depending on the report). You can then add the formula to the report conditions.

You may want to work with your consultant to help you with the exact format of the formula and condition so that it works correctly with your reports.

I hope that helps!

Just a caveat regarding placing a "security" condition in the Report Conditions: the user can delete conditions at the time of running a report. I recommend using the Conditional Print function an apply your formula to the data you wish to secure, preventing the end-user from tampering with the restriction.

Just a caveat regarding placing a "security" condition in the Report Conditions: the user can delete conditions at the time of running a report. I recommend using the Conditional Print function an apply your formula to the data you wish to secure, preventing the end-user from tampering with the restriction.

Would you use the same condition formula for Inquiries?

It's been many years since I've designed an inquiry and I don't recall if you can embed formulas deep into an inquiry in a way that would preclude the end user from modifying or deleting the security formula. In this regard, using the built-in security features may be best, but I'll defer to someone more actively involved with inquiry designs.