When we update a part, for instance we change models, we want the same part in all the associated assemblies to be updated automatically. Current process• Look up part to be updated • Click on Views and select where used (this is the list of assemblies the part currently exists in)• Update any details impacted by the change (AML, AVL, and Goals), new part and price• After save, we must go into each assembly and review where used• Update by locking, saving and unlocking, then into each assembly here. We have to follow this process to update each assembly it touches until we get to the Building assembly as that is our very top. Instead of going to each assembly and updating the part, we want this to happen automatically.

Hi Barnali, This should be possible by configuring the RelationshipType behavior which you can find more details about in the Just Ask Innovator help menu inside the client. It sounds like you'd want to make sure all of these relationships to your Part are configured to be Float relationships, so that they always point to the most recent version. However, this should be the default behavior set on most of these standard relationships. I ran a quick test in my environment by creating a very simple assembly called Parent with a single part in the BOM called Child, and I can confirm that they changes I made to Child were automatically visible when I went back to look at the Parent. Chris Christopher Gillis Aras Labs Software Engineer

Hi Christopher, I checked and the relationship types are configured to float. Is this related to part lifecycle map, workflows or Item types? Thanks, Barnali

Hi Barnali, I wouldn't think that this is related to the Life Cycle or Workflow. Would you be able to provide some steps to repeat this issue? I'm curious what specific piece(s) of information are needing to be manually changed after the part is updated. Chris

Hi Chris, I update (change model no) a part Say Part A, the state changes from released to preliminary. Then Click on Views --> Where Used, go to the assemblies where this part A is used. It shows the part A as released in the assembly. Unlock, update and lock the part A in the assembly so that the state changes to preliminary. After updating all assemblies, I change the Part A from preliminary to released. I would want this process to be automated so that I need not go to each assembly and update the part and change its state to preliminary. Ideally, when I change Part A, the changes and the state of Part A should reflect automatically in all the assemblies where it is used. Thanks, Barnali

Hi Barnali, Ah. I see what the problem is now. You were correct. This is indeed related to the Life Cycle Map. :) Each state in Life Cycle also has a behavior associated with it. I believe what you were seeing was that the parent assembly was in the Released state which gave it the Fixed behavior. Because of this, when you updated the child part, the parent remained pointing to the last released version of that part. In order to achieve what you're looking for, you'll need to edit each state in the Part's Life Cycle Map to have the Float behavior instead. Chris

Update Associated Assembly of a part automatically

14 Replies

christopher_gillis
New Member
6 years ago
Hi Barnali,

This should be possible by configuring the RelationshipType behavior which you can find more details about in the Just Ask Innovator help menu inside the client.

It sounds like you'd want to make sure all of these relationships to your Part are configured to be Float relationships, so that they always point to the most recent version. However, this should be the default behavior set on most of these standard relationships. I ran a quick test in my environment by creating a very simple assembly called Parent with a single part in the BOM called Child, and I can confirm that they changes I made to Child were automatically visible when I went back to look at the Parent.

Chris

Christopher Gillis

Aras Labs Software Engineer
- Barnali
  Ideator I
  6 years ago
  Hi Christopher,
  
  I checked and the relationship types are configured to float. Is this related to part lifecycle map, workflows or Item types?
  
  Thanks,
  
  Barnali
  - christopher_gillis
    New Member
    6 years ago
    Hi Barnali,
    
    I wouldn't think that this is related to the Life Cycle or Workflow.
    
    Would you be able to provide some steps to repeat this issue? I'm curious what specific piece(s) of information are needing to be manually changed after the part is updated.
    
    Chris

Forum Discussion

Update Associated Assembly of a part automatically

14 Replies

Recent Discussions

Welcome to the New Aras Community!

UI doesn't load for one user - anyone had a similar problem?

Aras 12 SP16 i can't find TOC editor

Using Aras to Manage Aras Upgrade Planning, Test Plans, Test Records

Batch Loader displays fail message when uploading mass data in PLMA