Timeline for Design practises against 50,000 row limit
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 31, 2016 at 11:39 | vote | accept | Prajith | ||
| Feb 26, 2016 at 16:09 | answer | added | Derek F | timeline score: 1 | |
| Feb 26, 2016 at 6:57 | comment | added | Prajith | @crop1645 The error we get when we go by the method you suggested earlier, is totally system generated right. That will happen as a part of system validation, which happens before the before trigger itself. So if my understanding is right, the execution stops even before any code comes into play. | |
| Feb 26, 2016 at 6:45 | comment | added | cropredy | is there a design where you catch the error and change the error message? | |
| Feb 26, 2016 at 6:41 | comment | added | Prajith | @crop1645 The error message that appears when a "duplicate" record is found needed to be customised. Couldn't find a way to customize the error produced by the system when it finds a duplicate record. It was affected the user experience. | |
| Feb 26, 2016 at 6:36 | comment | added | cropredy | why not a) create a formula field on A that is the synthesized lookup key and b) use WF to copy that value into a string field defined as Unique. Then SFDC does the dup checking for you | |
| Feb 26, 2016 at 6:25 | history | asked | Prajith | CC BY-SA 3.0 |