token.parent.New_label = 356;
Is this supposed to be possible? and/or is this just simply left out in the documentation regarding parent/child relationships?
token.parent.New_label = 356;
Is this supposed to be possible? and/or is this just simply left out in the documentation regarding parent/child relationships?
Yes, this is expected behavior. Setting the Parent Label Access is not really about encapsulation and preventing a child token from accessing things on the parent. It's more of an ease of use thing for determining what labels get accessed when you say token.MyLabel. On one end of the spectrum you give the token no access to parent labels so that all labels you read, write, or create using the token.LabelName syntax are on the child token. On the other end, the child token is just a proxy for the parent token and the token.LabelName syntax behaves exactly as if the child token were the parent token.
However, no matter what access you set, it's expected that if you explicitly access the parent token with token.parent then you have full access to the parent's labels.
Thanks! I’ve been struggling with some logic regarding split/join/batches and no preprogrammed activity settings seemed to suit my situation, i.e. until l found out that you can explicitly set parent token labels.
12 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.
Privacy | Do not sell or share my personal information | Cookie preferences | Report noncompliance | Terms of use | Legal | © Autodesk Inc. All rights reserved