0

For integration purposes I would like to store a few custom fields on User object which should be updated 10-30 times per day. Is it considered a good practice to have such fields on User object? Are there any side effects of updating User records with such frequency e.g. locking errors etc.?

2
  • 1
    Some more detail about what type of information these fields contain would be useful. Usually, Hierarchy Custom Settings are a good fit to store configurations for specific users, but it is hard to say given the level of information provided.
    – Adrian Larson
    Oct 26, 2022 at 16:56
  • @AdrianLarson It should have Large Text (10000) with average size about 2KB, Datetime, and another Large Text(10000) with average size 600KB. Custom Settings will not work here because of the size of the fields. Also there is a risk of hitting limit on 10MB for total Custom Settings size because of large number of users. We are considering either storing this info on User or on a new Custom Object. Oct 26, 2022 at 17:04

1 Answer 1

3

I would strongly consider putting these fields on a separate object. For one thing, any field you update on the User object shows up in the Setup Audit Trail, so making several such updates per user per day on a large user base would bloat that tracking to the point it would be borderline useless.

It will also be much less complicated to unit test any functionality layered on top of such an object, as it will not be setup data.

There are likely other risks associated which I have not touched on, but it is hard to see a compelling argument that adding these fields to User would be worth the costs already outlined.

1
  • I just checked on Dev Org. I have modified text field on User record. The change didn't appear in Setup Audit Trail. Also User record modifications are not mentioned in Monitor Setup Changes with Setup Audit Trail help.salesforce.com/s/… Oct 27, 2022 at 7:31

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .