Share
Report
66Hi,
Can anyone please explain to me the difference between :
a) xAccessRightsList::saveSecurityRights(keySet.packTouched() , ...
and
b) xAccessRightsList::saveSecurityRights(keySet.pack()
I was under the impression that the "pack() contained the entire security key set", whereas the "packTouched( )" ony contains the security key items that have been modified, is that assumption correct? I've had some unexpected results running a job that modified security recently...
Consequently, if in an X++ job you read the security for a specific existing group and domain, and then you modify some permissions, and finally save the changes with xAccessRightsList::saveSecurityRights(keySet.packTouched() --> will only the modified permissions be kept, and all others will be reset to the permissions set on the parent ? Or will the original (non-modified) permissions be kept, and will only the modified permissions be updated ?
Alternatively, suppose you write a job in X++ that creates a new group, sets the domain, and sets "Edit" permission on a specific table and a few of the table fields, and "View permissions on all it's other table fields. When you save the security key set for this new group, will that security key set only contain the "edit" and "view" permissions on that specific table and it's table fields. Or will you inherit security from any parents (for simplicity assume the Admin domain has no access at all) ?
Is there any differency between saving with "xAccessRightsList::saveSecurityRights(keySet.pack(),..;" and "xAccessRightsList::saveSecurityRights(keySet.packTouched()" in this scenario ?
Thanks for any insights !
Gert
*This post is locked for comments
I have the same question (0)
All responses (
Answers (
