why using current.update() is not recommended in befor BR ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-20-2016 06:19 AM
the BR will update any record based on specified conditions only. Then why using current.update() is not a good practice ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-27-2016 06:52 AM
Thanks a lot !
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-27-2016 07:48 AM
You are welcome. If your question was answered, don't forget to mark the appropriate response as correct so others with the same question can find it easily.
Thank you
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-20-2016 06:26 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-20-2016 06:29 AM
NEVER is a strong word. For those who don't understand it, OK. However there are RARE cases when it is required. I won't get in to that. Find me at Knowledge some time and we'll have a good talk about it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-20-2016 06:28 AM
Hi,
Avoid using current.update() to prevent recursions that impact system performance. The current.update() triggers business rules to run on the same table for insert and update operations. In a before or afterbusiness rule, this can lead to the rule calling itself over and over again.
It is unnecessary to use current.update() in a before business rule since these are saved automatically when the database is updated. After business rules are not intended to update current objects, so this is also not needed.
