List with "SELECT" keyword as values assigned throws exception

List with "SELECT" keyword as values assigned throws exception

poeychingneo
Observer Observer
15 Views
14 Replies
Message 1 of 15

List with "SELECT" keyword as values assigned throws exception

poeychingneo
Observer
Observer

[ FlexSim 21.1.1 ]

select_error.fsmI am learning on List and craft a small example as attached but it is throwing exception with the addition of "SELECT litres" clause. Is this a bug? Or I have some done something wrong?38975-select-error.png

0 Likes
16 Views
14 Replies
Replies (14)
Message 2 of 15

joerg_vogel_HsH
Mentor
Mentor

There are some conditions using a SELECT clause. The most important is, it MUST be a global list.

0 Likes
Message 3 of 15

poeychingneo
Observer
Observer

Thanks for the quick reply.

I've tried using global list and the same issue is seen. Furthermore, if the List properties has both "SELECT as quantifier" and "Assign SELECT..." checked the attached model works without error.

In regards to the requirements of the use of "SELECT" clause, the user manual has mentioned as below but they are not violated in this example too, even though this example is not using "SELECT" clause as quantifier.

  1. The clause references a dynamic label field.
  2. The clause references a label that is not explicitly defined as a field on the list.
  3. The clause references a non-dynamic field.


Hope to get more inputs/advice.


0 Likes
Message 4 of 15

jason_lightfootVL7B4
Autodesk
Autodesk

If you add 'litres' and 'Type' as fields to your list you will not get the exception:

39015-1619796839713.png

Message 5 of 15

poeychingneo
Observer
Observer

@jason.lightfootI have tried your suggestion (using both internal list and global list) but the exception is still seen. 😞

0 Likes
Message 6 of 15

arunTTT2P
Explorer
Explorer

Checking the "Use First Select Value As Quantifier" eliminates the exception. Check the attached model. Also added fields as @jason.lightfoot was suggesting.


39081-1620032457301.png

Regards,

Arun KRselect-error.fsm




Message 7 of 15

joerg_vogel_HsH
Mentor
Mentor

Without this option it does work as long as there are enough values to access on the list.

List_pull_SELECT.fsm

0 Likes
Message 8 of 15

poeychingneo
Observer
Observer

@Jörg VogelIn my attached model, it throws exception without the option. I wonder what mistake that I have made in my attached model to result in the exception?

@Arun KRIn my attached model, the behaviour will be different if the "SELECT ..quantitfier" is checked, and it will not meet the intended purpose which is only to read the value and write it as a label onto the puller token.

0 Likes
Message 9 of 15

poeychingneo
Observer
Observer

@Jörg Vogel Oh, l have tried changing the list to "global list" using my attached model. But it still throws exception.

0 Likes
Message 10 of 15

joerg_vogel_HsH
Mentor
Mentor

@pc neo, I know. It hasn't got to do with the SELECT clause it is more the fact that there aren't anything to pull and thus to assign a label to it.

0 Likes
Message 11 of 15

poeychingneo
Observer
Observer

@Jörg VogelIf there aren't anything to pull the token will wait at the "Pull from List". But it is now throwing exception. This sounds like a bug?

0 Likes
Message 12 of 15

joerg_vogel_HsH
Mentor
Mentor

Hi @pc neo, as I tested it, the problem occurs only if a backorder is issued. The mechanism tries to set labels for selected field values to the list main value. Because there is only a backorder and not an item to assert a label to, there is the throwing exception. If you allow a select clause be processed to lists returning successfully items, then you‘ll see that the mechanism works as intended. If you think, that the limits of the select clause is a bug, then it is a bug.

I tried to combine select and sum clause to get the total of a query, but that doesn’t work either, even if I tried to have a successful query. A successful select query returns only an array.

0 Likes
Message 13 of 15

Ben_WilsonADSK
Community Manager
Community Manager

Hi @pc neo, was jason.lightfoot's answer helpful? If so, please click the red "Accept" button at the bottom of their answer. Or if you still have questions, add a comment and we'll continue the conversation.

If we haven't heard back from you within 3 business days we'll auto-accept an answer, but you can always unaccept and comment back to reopen your question.

0 Likes
Message 14 of 15

poeychingneo
Observer
Observer

hi @Ben Wilson the suggestion from @jason.lightfoot does not resolve my issue. After getting inputs from many others particularly from @Jörg Vogel I believe it may be a bug and I will send an email to dev@flexsim.com.

Thank you 🙂

0 Likes
Message 15 of 15

poeychingneo
Observer
Observer

@Jörg Vogel thank you for your input. I will email to dev@flexsim.com on this. Though it is not a critical issue for me now.

0 Likes