Restriction of permissions on one General Ledger Setup field

(0) Share

Report

Posted on by AntonioKD

432

Hello everyone,

I am creating permission sets for users in BC Cloud. I need to revoke permission to modify one field in General Ledger Setup - "Allow Posting From". I know that I can delete permission to Modify all the object (Table Data ID 98) but can I cancel permission to modify only one field? I have tried with Security Filter to this object but it doesn't work. Do you have any idea how to setup this or I need to delete Modify permissions for entire object?

Thank you in advance!

I have the same question (0)

All responses (5)

Answers (3)

Suggested answer

JAngle 152 on at

Like (1)

Report
Copy link

Link copied!

specific field security can be achieved with an appsource extension or with a customisation. There are a few to look at but here is one example: appsource.microsoft.com/.../pubid.fenwicksoftware|aid.fg03|pappid.9c635c18-e65b-4aba-b78c-e35552de4c60

The standard way to handle this scenario is to use the in built field monitoring - some detail here: docs.microsoft.com/.../across-log-changes

You can get more advanced with this if you use: docs.microsoft.com/.../telemetry-field-monitoring-trace

Was this reply helpful? Yes No
Verified answer

Lars Lohndorf-Larsen Microsoft Employee on at

Like (1)

Report
Copy link

Link copied!

Hello,

As Josh says, there are solutions for field-level security. Basically you need to use either field triggers or events, and add some .al code there to check if the update is to be allowed. Or maybe you can personalize the page and removing the field, but then users may find a way to personalize the page back. So out of the box, there is no good (no-code) way to get field level security.

Was this reply helpful? Yes No
Verified answer

Alfredo_Iorio 1,268 on at

Like (2)

Report
Copy link

Link copied!

Permission filters on table fields are not standard.

A workaround is to customise a Profile (Role) and hide the fields from the page.

Then you can remove page personalisation so the user can't add the fields to the page. The downside of this solution is that users are locked from personalising any page which might be annoying.

Was this reply helpful? Yes No
Suggested answer

Inge M. Bruvik 1,165 Moderator on at

Like (2)

Report
Copy link

Link copied!

One workaround if there are not too many users can also be to simply administrate the posting allowed dates from the User Setup instead of the finan G/L Setup. The user setup is less risky to have access to and it will override what is in the G/L setup. But you need to set it on user level.

Then you can deny modify on the G/L setup.

Was this reply helpful? Yes No
Verified answer

YUN ZHU 99,090 Super User 2026 Season 1 on at

Like (3)

Report
Copy link

Link copied!

Hi, As mentioned by several experts above, there is no field-level permission control in BC. If customized, there are many solutions.

But I'm in favor of Alfredo's method, which doesn't require customization. Just hide it from the page.

Hope this helps as well.

Thanks.

ZHU

Was this reply helpful? Yes No