When you’re testing your methods in a Cycle, in the Cycle Settings, you can find an option called Collection Splitting. Let’s take a look at Collections Splitting and what it means.
What is Collection Splitting?
Collection Splitting allows lists of data returned in the method response to be split into separate transactions.
When a collection of data is returned, We can manipulate the data by the following options:
- Trigger (First Step) – Lists of data will be split by transactions triggered by the First step
- All Steps – Lists of data will be split into transactions triggered at each step.
- None – Lists of data will be compiled into 1 collection with no collection splitting.
Generally when testing methods it’s advised to set collection splitting to ‘None’ to show that each request contains the full collection of data. This should allow you to see all of your data grouped together in one collection.
Collection Splitting can be used when you don’t want a list of data to move through your Cycle in a single Transaction. If you do, then you can disable Collection Splitting.
Splitting a list into separate items results in each item moving through a Cycle in its own Transaction. This can be beneficial in situations where you’re retrieving further lists of data for each item in an initial list, to avoid the data becoming too complex and difficult to process.
Configuring Collection Splitting
You can set Collection Splitting at two locations:
- from the Cycle Settings button along the top of the Builder
- using the Step-level overrides found in each Step’s Step Setup > Advanced Settings area
The option on a Step will always override the Cycle Settings option.