Comentario
12-06-2024
02:31 AM
12-06-2024
02:31 AM
Reporting a scenario supporting this improvement idea:
- Model A has nested links: model B and Model C (both attachments)
- Model A gets linked in the HOST file (with both model B and C getting put on the same active workset of the HOST when linked).
- Model A receives a NEW model D as an attachment.
- Model A gets reloaded in the host. Important to note: In this scenario, all previously existent (legacy) nested links remain on their old workset, but the new one gets placed in the host file on the active workset of the HOST model during the reload operation.
- Should any of the Worksets of the nested links would need adjustments retrospectively, the only way for the user would be to remove and recreate the attachment in Model A and reload model A in the Host, with the active workset set to the desired one. Unfortunately this action would ruin and delete previously placed tag and dimension elements associated with the nested link in question.