Inventor General Discussion

Inventor General Discussion

Active Member
9 Posts
0 Kudos
Registered: ‎12-22-2010
Post 1 of 3

Cyclic Dependency problem

431 Views, 2 Replies
09-18-2012 07:55 AM

first off, I do not know what this error I keep getting on .idw's of top level assemblies.

I have problems with views not updating after changes were made.


This was a layout done in Inventor 2011 and I made changes to the .iam (2013), but I cannot get them to update on the .idw's.

The tree in the .idw's has all my views shown with a "question mark" and I cannot edit anything. I know I could probably delete them and re-insert them, but I have ballons and parts list that I do not want to re-do.


I also tried to update between Master & Default view in the Assemblies, no luck.




I attached the Cyclic Dependency error dialog box.


thanks for your time


359 Posts
38 Kudos
Registered: ‎05-20-2008
Post 2 of 3

Re: Cyclic Dependency problem

09-19-2012 01:45 AM in reply to: 2013auto

Hi Brian,


Could you attach the dataset or send me @ for further investigation?

River Cai

Inventor Quality Assurance Team
Autodesk, Inc.
Active Member
9 Posts
0 Kudos
Registered: ‎12-22-2010
Post 3 of 3

Re: Cyclic Dependency problem

09-19-2012 07:09 AM in reply to: Yijiang.Cai

To River Cai,

I ended up fixing my problem.

to re-cap - This is opening a Top Level .idw.


It was a problem with resolving fasteners from the Content Center. The system would ask to resolve and then tell that they were not part of the active project.

The particular fasteners would show up fine after that, and every view was fine (I could open from the .idw's).


But when I would close the .idw and reopen, the same fasteners needed resolved. I finally did a "Replace from Content Center" and that worked.


There must be some minor changes to the fastener name or something . . .


Frustrated but fixed.



Post to the Community

Have questions about Autodesk products? Ask the community.

New Post
Are you interested in helping shape the future of the Autodesk Community? To participate in this brief usability study, please click here. Your time and input is greatly appreciated!