Timeline for Populating Dynamic field using Workflow Rule or Trigger instead of Formula Field
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 16, 2015 at 10:15 | comment | added | Davin Casey | Yes sorry that's what I meant, populate a plain text field with Manager.Username or similar and then filter by that in your report. | |
| Oct 16, 2015 at 10:12 | comment | added | Aryansh04 | When you say, Yes the field can be replaced with text field updated by trigger Can you explain how? Trigger will populate value only once based on the event. In my case, the value needs to be changed depending on the logged in user. Secondly, as per the article you shared, my formula field is Non-deterministic, so Indexing is not possible. What is possible is that I incorporate the Formula logic into Report filter itself. | |
| Oct 16, 2015 at 9:56 | comment | added | C0DEPirate | I agree with @davinC, when you can achieve the functionality using Formula, why to use Apex trigger or WF. On the top of it trigger or WF will execute on when DML is performed. Also if your data is taking longer time to load , it is performance issue of Database not because of Formula. | |
| Oct 16, 2015 at 8:25 | history | answered | Davin Casey | CC BY-SA 3.0 |