question

Claire Krupp avatar image
0 Likes"
Claire Krupp asked Phil BoBo commented

Pull from Label value on List not working properly

I need to pull one item from a rack of 15. I am using an Internal List in Process Flow, with the "SELECT labelName" query. It's copied line by line from the PF Tutorial with the rollQuantity label. I have also used this technique in two other models. This one looks identical to those, but when the Pull from List happens it takes the whole token off the list and shows it as satisfying only 1 pulled item. (I also notice the puller token label "rackqty" has changed from 1.0 to 15.0.)

Originally I had partitions and a lot of labels calculated from other labels but I have taken all that out. I also took out the Max Wait Timer.

I've tried it with or without an added "WHERE" clause. And with and without the dynamic box checked on the list. (It works without "dynamic" checked in my other model!)

I have no idea why it is not working. Can anyone figure it out??

test-pull-from-label-value.fsm

Thanks!

FlexSim 19.2.0
process flowpull from listselect query
5 |100000

Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

1 Answer

Matthew Gillespie avatar image
0 Likes"
Matthew Gillespie answered Phil BoBo commented

In the List's General tab, uncheck Assign SELECT Values to Puller Labels and check Use First SELECT Value as Quantifier.

See this question for more details. https://answers.flexsim.com/questions/71911/query-select-a-label-of-a-list-with-the-new-option.html

· 2
5 |100000

Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

Claire Krupp avatar image Claire Krupp commented ·

Thanks @Matthew Gillespie that did the trick!

I sure do wish you guys would not make a change to the default behavior like that without issuing DETAILED upgrade notes! I wasted 5 hours trying to debug it!

0 Likes 0 ·
Phil BoBo avatar image Phil BoBo ♦♦ Claire Krupp commented ·

Sorry the release notes didn't mention the change to the default behavior. That was an oversight on our part.

0 Likes 0 ·