Hi @Philip_Bassham
The solution to this is to write a code step in Zapier which splits the incoming string of comma separated variables into blocks of 24 and then to return these in an array of objects. This causes the following steps (starting withe the routing which creates an array of objects with a single record id in each) to run for each group of records. So if you split the original incoming data into 24 such blocks and each of these has 24 individual records then the subsequent processes will run for 24 x 24 = 576 records. Here is a sample of suitable code in Javascript:
//this splits the articles up into chunks of 24 to avoid the Zapier limit…
if (inputData.allArticles == null) {
allArticlesArray = [];
} else {
var allArticlesArray = inputData.allArticles.split(",");
}
var outputElement = [];
var outputElementItem = “”;
var articleNos = allArticlesArray.length;
var i=0;
while (allArticlesArray.length > 0) {
outputElementItem = allArticlesArray.slice(0,24);
var outputElementItemObj = {}
outputElementItemObj.record = outputElementItem
allArticlesArray.splice(0,24);
outputElement.push(outputElementItemObj);
}
return(outputElement);
The input Variable allArticles may have up to 576 comma separated elements, and the array of Objects, outputElement, is an array of objects each containing comma separated lists of up to 24 of these.
You could put some error trapping code in here (for example to check the original allArticles variable doesn’t contain more that 576 items).
I haven’t yet had a need to try, but I assume you could create another ‘layer’ here so that you could process 24x24x24 (13,824) in a single Zap - and so on.
