Community
If you are on 2021 or earlier you can use level of detail to suppress them, but then you won't see them.
You could probably use model states to do this too.
I assume you aren't using vault or this wouldn't be a problem.
Expert Elite
Inventor Certified ProfessionalIf you are on 2021 or earlier you can use level of detail to suppress them, but then you won't see them.
You could probably use model states to do this too.
I assume you aren't using vault or this wouldn't be a problem.
Expert Elite Inventor Certified Professional
Vault copies all the files to your local drive. You get an icon to say a file has been updated, but it doesn't do it until you tell it to and there aren't any pop up messages whilst working.
It is however not as straight forward as just installing vault. It needs doing properly and people will need training on it.
Expert Elite Inventor Certified ProfessionalVault copies all the files to your local drive. You get an icon to say a file has been updated, but it doesn't do it until you tell it to and there aren't any pop up messages whilst working.
It is however not as straight forward as just installing vault. It needs doing properly and people will need training on it.
Expert Elite Inventor Certified Professional
Hi Johan,
I think indeed, this is what Vault is for. It helps you manage versions and who owns what at any given moment. Actually, the behaviors can be replicated without Vault. Let's say you have a data storage, which contains the latest and greatest. So, you make a copy of the entire assembly locally. Another user do the same. But, you guys work on different portion of the assembly.
After you are done, you guys can provide the files you changed back to the data storage. Kind of like a simplified manual Vault workflow.
However, it will only work if the two portions do not overlap. And, there isn't any dependency between the two portions. If there is any dependency, you will run in to confusing behaviors and failures fairly easily.
Many thanks!
Johnson Shiue (johnson.shiue@autodesk.com)
Software Test Engineer
Hi Johan,
I think indeed, this is what Vault is for. It helps you manage versions and who owns what at any given moment. Actually, the behaviors can be replicated without Vault. Let's say you have a data storage, which contains the latest and greatest. So, you make a copy of the entire assembly locally. Another user do the same. But, you guys work on different portion of the assembly.
After you are done, you guys can provide the files you changed back to the data storage. Kind of like a simplified manual Vault workflow.
However, it will only work if the two portions do not overlap. And, there isn't any dependency between the two portions. If there is any dependency, you will run in to confusing behaviors and failures fairly easily.
Many thanks!
Johnson Shiue (johnson.shiue@autodesk.com)
Software Test Engineer
You shouldn't just get them randomly.
If you open a part from your assembly to edit on it's own and someone else has edited it you may get a message.
You shouldn't get constrain issues because they will be working with a local copy of the file so nothing will have been updated on their end. It's only if they choose to refresh the files from the vault add in.
Expert Elite Inventor Certified ProfessionalYou shouldn't just get them randomly.
If you open a part from your assembly to edit on it's own and someone else has edited it you may get a message.
You shouldn't get constrain issues because they will be working with a local copy of the file so nothing will have been updated on their end. It's only if they choose to refresh the files from the vault add in.
Expert Elite Inventor Certified Professional
Forums Links
Can't find what you're looking for? Ask the community or share your knowledge.
Post to forums
