SplitEvery Considerations

Purpose

Inserting the tag allows code to be broken up and processed into chunks.

For example: The following line of code breaks up the processing into chunks of 5 records at a time.

<splitEvery> 5 </splitEvery>

Concern and Considerations

The concern with splitEvery:

• Cannot work within HTML tags such ,, tags.

  Consideration when using splitEvery:

  • The only way splitEvery works effectively is placing it on the parent level and leveraging a component template for every record queried.
  • When splitEvery is leveraged, an SD Job is supposed to be created.
  • splitEvery is typically leveraged to split jobs and stay below the APEX CPU time limit error.
• No related lists can be encapsulated in HTML tags in the parent template even if a related list using splitEvery is not encapsulated in HTML tags itself.
• Does not work properly when placed in a component template.