Jump to content
Simio Forum

Welcome to the Simio Forum

Welcome to the Simio Forum! Experience the full experience of the forum by becoming a Simio Insider! You must be an Insider to post on any forum!



Simio Employee
  • Content Count

  • Joined

  • Last visited

  • Days Won


Posts posted by KatieP

  1. It looks like both the person and bag are from the same EntityClass: ModelEntity. Assuming that is true, before the CreateStep put Assign: Variable: ModelEntity.StringStateName New Value: ModelEntity.Name On the Create Step, set Create Type:CopyAssociatedObject and EntityType:Bag. ALL the personEntity states and properties overwrite the bagEntity's. If bag entity has settings that shouldn't be overwritten then you can subclass ModelEntity to make a bagEntityClass. If the bagEntity is from a subclass of the ModelEntity, then only states and properties in common change. No additional Assign is needed. The person and bag EntityClasses could be unrelated. If so, an additional assign Step is needed after Create with Variable: BagClass.StringStateName1 & NewValue: ModelEntity.StringStateName Then only that state changes.

  2. In Simio, all tables exist at the top level, e.g. in the main model. Any “outside” data that is referenced inside an object or submodel must be passed into the submodel via properties defined on that submodel. The mechanism for passing in sets of data like found in Tables is to define a Repeat Group property. This Repeat Group is then used to store the information from the top level model.

    The SimBit Top Level Model (from project Hierarchy With Tables) is an example of using repeating groups.

    In Help Using A Custom Object In A Model: Data Tables explains how to move your data from the submodel to the main model, map it to the Repeating Group and convert the submodel table to a repeating group in a few short step.

  • Create New...