ACL creation through datasource

[Arun96]

Hi All,

I have come across a requirement to create ACLs through datasource. Details will be provided in excel sheet and based on that ACL records needs to be created.

While working on this requirement, I was trying to populate value on Name filed in ACL form.

Name field is a composite type field, I was not able to understand the combination of fields used for the Name filed.

Please let me know if you have any idea about this and also your thoughts regarding the creation of ACLs through datasource.

Thanks,

Arun

[Tony Chatfield1]

Hi, the need to create ACL's should be very infrequent and all ACL's should undergo careful testing before deployment to a production environment' as discrepancies could cause platform wide security\access errors; meaning that I would not recommend this approach as best practice.

Can you clarify the use case that drives this requirement?
Also what part of the ACL 'name' do you not understand?
The ACL 'name' simply identifies the table, or table and field combination, that the ACL applies to and this may include a * wild card to indicate all values.

[Arun96]

Hi Tony,

I agree with your statement that it is not a best practice.

This requirement is to restrict read access of custom fields only to admin in multiple tables.(right now around 350 fields in multiple tables and many more to come).

About the 'name' field, how I can populate value in this field through script If I want to?Could you explain how can we achieve this through script.

Thanks,

Arun

[Tony Chatfield1 · Accepted solution]

Testing very quickly with GlideRecord in a background window, then the name field was populated simply using a string 'tableName.fieldname', but I did not test\validate the resulting ACL.
I recommend that you go back to your management team and advise that this approach would not be best practice and there is considerable risk to the instance.