FSC RBL updates without Error during Bulk Data Load of Financial Accounts - Ideas - Salesforce Trailblazer Community
Trailblazer Community

All Ideas

Idea Details

Post an Idea
1,280  Points
Idea has been posted. Give it an upvote or downvote.

FSC RBL updates without Error during Bulk Data Load of Financial Accounts

Financial Services Cloud

When a Financial Service Cloud ( FSC ) Individual or Household has multiple Financial Accounts updated or created via the Bulk API, the Rollup by Lookup ( RBL ) framework should process without a platform Error.
At minimum, the RBL framework need to successfully complete daily Bulk data batches in a standard FSC org with a moderate amount of Individual, Household, Financial Account,and Financial Account Roles data.
Expected Results: FSC RBL Apex jobs complete without Error.

Actual Results: FSC RBL Apex jobs error out which causes RBL balance values to be incorrect. Errors experienced include the following:
  • Row Locks ( UNABLE_TO_LOCK_ROW ) from FSC RollupbyLookupHandler Apex Class
  • Apex CPU Timout  ( System.LimitException: Apex CPU time limit exceeded 
  • Apex Jobs Queued ( Queueable )
  • Query Timeout ( QUERY_TIMEOUT )
  • Long Running Queries ( Map_put.out )
Workaround: Knowledge Article: Household and Individual Totals are not in sync after Bulk inserting or updating Financial Accounts ( 000270275) https://help.salesforce.com/articleView?id=000270275&type=1 



Merge Idea · Flag

  • Upvotes
  • Downvotes



from AppExchange


No results found.

Help us to keep IdeaExchange clean by pointing out overlapping ideas. We'll investigate your suggestion and merge the ideas if it makes sense.



Thanks for your merge suggestion. We will review it shortly and merge the ideas if applicable.

Salesforce takes abuse situations very seriously. Examples of abuse include but are not limited to posting of offensive language or fraudulent statements. To help us process your request as quickly as possible, please fill out the form below describing the situation. For privacy and security reasons, the final outcome of an abuse case may not be revealed to the person who reported it.


Thank you for your feedback. We take abuse seriously and will investigate this issue and take appropriate action.