MAPSB (Manufacturing Associative Part Structure Browser).
When you update top node in downstream structure with command “Update To Current Upstream Equivalent Object”, all nodes with upstream children are checked out. See attached PowerPoint.In 11.0 this was not the case, it is a new behavior in 11.1 as a workaround for PTC R&D to secure functionality in some specific cases.
This solution hits customer hard that does not have this specific problem.
A better solution is to have a preference so user themselves could choose if they want all check out or not.
This means that customers that does not have this specific way of working also are satisfied with MAPSB and get rid of a lot of extra work every day.
I agree that these checkouts are unnecessary and cause undo work to our users. This really needs to be remedied.
For us this is a major issue! We are in the shipbuilding industry with extreamly large structures. An update of the top node eqv.link will cause hundreds of downstream Parts to bechecked out! This is not acceptable.
Regarding to article CS298190, this is inteded behaviour. Does anybody know why this was introduced? What problem was solved when having it like this?
I guess none of us know why this was changed. However, I suppose that it was to simplify the code of MAPSB. That was also the reason why PTC removed a basic functionality of MPMLink with Windchill 11.0: Explicitly set which attributes should be transferred from upstream to downstream on create/update. - The documentation for this was changed afterwards... unbelievable.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.