Timeline for How to exclude the "System" from a validation rule?
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 2, 2018 at 17:28 | answer | added | Maria Huemmer | timeline score: 0 | |
| Jul 4, 2017 at 13:25 | vote | accept | Juice♦ | ||
| Jul 4, 2017 at 13:25 | answer | added | Juice♦ | timeline score: 0 | |
| Apr 20, 2017 at 20:58 | comment | added | Juice♦ | @AMM Creating a fake user with sysadmin access was the only workaround I could find. | |
| Apr 18, 2017 at 19:38 | comment | added | AMM | I'm looking for the same thing. We DO have a "robot" user account for automation from outside of SF to get into the Org. | |
| Jan 10, 2017 at 0:41 | comment | added | Juice♦ | I think I'm just going create a fake user for this. | |
| Jan 10, 2017 at 0:40 | comment | added | Juice♦ | When I check the syntax I get an error, "Error: Field Name does not exist. Check spelling." | |
| Jan 10, 2017 at 0:32 | comment | added | cropredy | does $User.Name = 'System' not work or perhaps $User.Name = 'Automated Process'? | |
| Jan 9, 2017 at 19:41 | history | edited | battery.cord | CC BY-SA 3.0 |
added 2 characters in body
|
| Jan 9, 2017 at 16:45 | review | First posts | |||
| Jan 9, 2017 at 16:56 | |||||
| Jan 9, 2017 at 16:45 | history | asked | Juice♦ | CC BY-SA 3.0 |