topic Re: Post batching can I use batched label array to query pull request from list? in FlexSim Forum

Post batching can I use batched label array to query pull request from list?

jkhedekar — Tue, 29 Jul 2025 18:52:01 GMT

I am batching 3 tokens. The batched qty can be 1,2 or 3. After batching I release a single token since I want to use it to run in a subflow. Post that I have a pull function that pulls from a list. So I am batching based on a label called destination. So I can easily use WHERE destination = puller.destination. However, after that I have label called Initialdestination, which during batch I make it an array so post batching it looks like ["destination1", "destination2", "destination3"]. I want to use an if else in Pulls query section where I say.

WHERE destination = puller.destination AND IF puller.batchedqty > 1 BEGIN Initialdestination == puller. Initialdestination[1] ... and so on

Is it possible to do something similar?

Flexsim version: 23.0

Re: Post batching can I use batched label array to query pull request from list?

moehlmann_fe — Wed, 30 Jul 2025 06:30:08 GMT

If the goal is to pull one entry for each initial destination value, then use three separate tokens. If the goal is to pull something that matches any of the values in the array you can use "WHERE Initialdestination IN puller.Initialdestination"

Re: Post batching can I use batched label array to query pull request from list?

jkhedekar — Wed, 30 Jul 2025 15:40:50 GMT

Yeah the problem is not if I were to pull any. But I want to pull the the same token which has a unique ID label. So if I am batching 2 tokens which now is converted to 1 with unique ID label as an array [232,543]. I want to then pull 2 labels from the list with the same unique ID. So required and requested pull qty is token.batchedqty which is a label to see how many have been batched.

Re: Post batching can I use batched label array to query pull request from list?

moehlmann_fe — Thu, 31 Jul 2025 06:03:09 GMT

If the IDs are unique then you can still use "WHERE Initialdestination IN puller.Initialdestination". It would only have been an issue if the same value can appear multiple times because then the query could pull "232" twice instead of "232" and "543".