Hi,
When pulling from a list, I have mostly been using WHERE ____ = token.[label]
However, I recently got a few errors and noticed that if I changed it to WHERE ___ = Puller.[label], then the query worked perfectly.
Why is it that the token reference worked in some cases? How can I find out what the difference might be between these lists? I would prefer the token reference to work because that is the default action when writing a query, not that typing Puller is any harder. Just curious.
It is always correct to use "WHERE val = Puller.LabelName", and I'm fairly confident that it is never correct to use "WHERE val = token.LabelName". In fact, I'm somewhat surprised that it works for you in certain cases. I recommend you always use Puller.
As for why you use "puller" and not "token" in a list query, the quick answer is that you can make any node the puller, including a token, a Queue, a TaskExecuter, etc. Since anything can be the puller, it doesn't make sense to assume that "token" is the puller.
Thank you for the explanation. I will begin using Puller from now on, however is the puller defined somewhere in the list settings or activities since you said any node could be a puller?
If you are in Process Flow, the Pull From List activity lets you specify the puller:
16 People are following this question.
FlexSim can help you understand and improve any system or process. Transform your existing data into accurate predictions.
FlexSim is a fully 3D simulation software environment. FlexSim can be used to simulate any process in any industry.
FlexSim®, FlexSim Healthcare™, Problem Solved.®, the FlexSim logo, the FlexSim X-mark, and the FlexSim Healthcare logo with stylized Caduceus mark are trademarks of FlexSim Software Products, Inc. All rights reserved.
