Why would a Before Insert Business Rule on sys_user table affect existing records?

[Chris Cardenas]

We had a situation where we tested a Business Rule that runs Before Insert on the sys_user table.

The goal was to target new account creations and adjust them to Web service access only

However shortly after creation it affected a large amount of already existing user records.

Why would this happen? I believed that a Before Insert rule would only run/affect a new record being created?

[Bert_c1]

Set Advanced to 'false' if you're not using a script there.

[Joni V B]

@Chris Cardenas ,

Are you sure that the business rule you are showing was responsible for the changed records?
If the configuration is 'before insert' it won't do anything on existing records as you expect.

Maybe it was changed along the way? If you look at the version of the business rule, was it active at any point with 'update' also checked?

Best regards,

Joni

[Ankur Bawiskar]

@Chris Cardenas 

before insert will run only for fresh insert and not for existing record.

Did you check any other BR or script update it for existing records?

[Ankur Bawiskar]

@Chris Cardenas 

Thank you for marking my response as helpful.

As per new community feature you can mark multiple response as correct.

If my response helped please mark it correct so that it benefits future readers.

[jcmings · Accepted solution]

As some of the other commenters have posted, something else is causing the issue; you are correct that the Insert BR will only fire on new record creation. I'd look at other BRs and scheduled jobs you have.