Demperical(GlobalTable) returns the wrong values of another GlobalTable

[amelie_c]

[ FlexSim 20.0.0 ]

As you can see in the model, for every order entering the shop floor, a certain volume is assigned. The distribution of these volumes are dependent on the type of the orders (LEM,REM,LS). I have used three global tables for the values of the volumes (one global table for each type of order).

When you look at the process flow, you can see the assignment of the volume in assign volume. Type 1 is LEM, type 2 is LS and type 3 is REM. For LS and LEM the correct volumes are assigned to the orders when you run the model, for REM, the wrong values are assigned. I think these are the values for the type LS.

Can someone help me where there is a mistake for the volume values of the REM orders ?

Thank you ! huidigepoging4.fsm

[Matthew_Gillespie · Accepted solution]

You're assigning a "type" label on token.item and then using "token.item.type" for the case function. However, you'll notice that the word "type" is purple indicating that this is a property and not a label value. What's happening is that the Variant class has a "type" property that tells you what type of Variant it is. (See Variant.type for more information)

Basically, you need to change all your "type"s to "Type" so that you get the label called "Type" on the item instead of getting the variant type of the token.item variant.

[joerg_vogel_HsH]

@Matthew Gillespie, isn’t there the mechanism to test, if the label exists by the question mark. I have read or heard that this mechanism makes it possible to get values from label names matching with property name?

[Matthew_Gillespie]

You put a # in front of the label name

token.#type