Security - update rights to only a few fields of a table

(0) Share

Report

Posted on by Community Member

Hi guys

I've got another interesting requirement: role x has to be able to edit only a specified 4 fields of total 20 of a certain table.

The way i've done this is: Role-> permissions node -> tables -> drag table -> set EffectiveAccess to update.

Now the role has full update access to the table in all the forms. Now, i've dragged all the fields of this table onto the permission and gave the 16 other fields Read access.

This doesn't feel clean. Whenever we'd add a new field, this role would automatically get update access to the field. Which is not always desirable.

Doing it the other way around (set table read access but add fields with update access) raises an error: Access for field ContainerNo exceeds access for table ADUContainerFields.

Any ideas?

*This post is locked for comments

I have the same question (0)

All responses (5)

Answers (1)

Community Member on at

Like (0)

Report

Hi Crispin

This article explains exactly what i did but via AOT.

The problems still exists: new fields would get full authorization by default (which is not desirable).

Was this reply helpful? Yes No
Verified answer

André Arnaud de Cal... 301,053 Super User 2025 Season 2 on at

Like (0)

Report

Hi Tim,

There is no workaround for this or you would go in another type of customizations. When you add a new field, it would be done based on a FDD or another request. Part of the procedure would be mentioning to also add the new field into the permissions for this specific table.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Agreed. But you know how security is usually the "forgotten child" :-)

Thanks though.

@Crispin: i was messing around with the "do not override" checkbox but this doesnt get the desired result.

Was this reply helpful? Yes No
André Arnaud de Cal... 301,053 Super User 2025 Season 2 on at

Like (0)

Report

Hi Tim,

As of the introduction of AX2012 I was aware you have to think of security at any development effort. I do agree that in many cases it is a "forgotten child", but it shouldn't be...

Was this reply helpful? Yes No
Joanna Demetriou 355 on at

Like (0)

Report

Hello everyone

I'm very surprised that this is not possible in AX..

I know this post is nearly a year old so has anything changed in the meantime?

I understand that security shouldn't be forgotten, but let's be realistic.

It's really hard to keep track of these things especially when working on a standard industry solution while security artifacts are very specific to customers.

Every time a table is extended with a new field, you'd have to check all customer installations to ensure that their security elements get updated?

How realistic is that?

This doesn't seem right.

Above all a solution should not impose a thread, especially a security thread.

How can MS provide exactly one way of doing this and that way by default causing a security breach?

The default behavior should be the safe behavior.

Am I missing something?

Thanks

J

Was this reply helpful? Yes No