Vault Basic Library red dots

[Cadkunde.nl]

Hello forum,

I have a company using Vault Basic 2024

Company wants to lock their standard to prevent engineers from accidently checking out files.

So we made a Library folder in the vault:

We have a Company.ipj with Library folder set:

And we have an EditLibrary.ipj with:

When we have the company.ipj on and look in the Vault brower we see all the files that are in the libary with a red dot:

Am I doing something wrong in the settings?

We prefer white dots 🙂

Perhaps I need to set library folders in vault and not in IPJ or only in IPJ and not in Vault?

So if anyone can help me with this I am very grateful.

BONUS:

When using EditLibrary.ipj, you always get this message:

[ihayesjr]

@Cadkunde.nl 

The Red Dot tells you that the local file versions are not the latest versions on disc. Perform a Get on the Library to download all of the latest files into the workspace.

[Cadkunde.nl]

@ihayesjr Sorry if i wasnt clear

All files in library are always red, unable to make white, unless we change to the editLibrary.ipj

[Cadkunde.nl]

Anyone who can help with this problem?

[CGBenner]

@Cadkunde.nl 

Do you use Vault Content libraries?

It also looks like you are using a separate project for your Content Center components?  If that is the case and the Libraries are in the Vault, you will always need to activate that project before you can update those files from the Vault.

[Cadkunde.nl]

@CGBenner @ihayesjr 

Thanks for the replies.

We have Vault Libraries, and a seperate project file to edit the library.

With the main project file the engineers use, the parts in the library are always showing red dots.

Is this normal behaviour or am I doing something wrong?

[arkad_s]

How exactly you are opening your files? From main grid in Vault Client or maybe from Where Used/Uses tabs? Does it work when you use Open from Vault in Inventor? 

Can you try to Get latest file and its children before attempt to open? See my example:

I tried to run into the same as you described and it only happens when I forced to download historical version of library file to my local workspace before opening parent file (and it is "fixed" when I get latest versions manually and opened again). Tested in Vault 2024.3.1.

Regards,
Arek

[Cadkunde.nl]

@arkad_s 

This is the Vault Tab inside Inventor: 

We see red dots for all files inside library folder when using the project file that has set these vault library folders as library.

The files are up to date, but we see red dots instead of white.

All the information how we set up libraries and our project files are in the first post

[arkad_s]

@Cadkunde.nl 

Thanks but these are not helping me to see potenial cause. Would you mind giving us more infomation as I asked in the previous message? I tried using the same settings with two project files but I cannot run into the same (apart from that one situation I described above).

Or another option - you might start a support case so someone can jump in and check things toghether with you.

[CGBenner]

@Cadkunde.nl 

In your main Project file, are these libraries configures?  Or are they only configured in the Project for Content Libraries?

[Cadkunde.nl]

Yes, in the main project file, we have library configured:

And it matches vault structure:

But every file in the Library has a red dot, when opening files with the main project.

Our main project file (and library project file) is located in Vault Explorer($)

[CGBenner]

@Cadkunde.nl 

Thanks, I was thinking more about you Inventor Project.

[inventor]

Hi everyone, 

Since @Cadkunde.nl is on summer holiday, I'll try to give some more info on this subject (I'm a user of this Inventor  and Vault setup).  

Our new library is not a desktop content library, bus just a library folder with parts and assemblies placed in it:

So this library is not available in the "configure libraries" screen:

Hope this helps

Regards, Ruurd

[CGBenner]

@inventor 

Thank you for clarifying, I was completely on the wrong track!  @ihayesjr do you have any other suggestions for these guys?

[CGBenner]

@arkad_s @gandhey do either of you have any ideas on this topic?

[arkad_s]

@CGBenner I cannot reproduce the same on my side but there are some questions that I asked before earlier, that probably were missed:

"How exactly you are opening your files? From main grid in Vault Client or maybe from Where Used/Uses tabs? Does it work when you use Open from Vault in Inventor?"

"Can you try to Get latest file and its children before attempt to open? See my example:"


And still there is an option to raise support case so someone can jump in and look together with customer.

[CADAutomation_nl]

This is a familiar problem to me that I have seen more often with Vault Basic users.

In both cases when I place in a library component I also get the red dots.

When I use the Libraryeditor proj

ect file to open the file in question there seems to be nothing wrong.

So I am very curious what the possible cause is.

In the video you see how I get the files in the assembly environment, and when I open the file with the libraryeditor file

[BDCollett]

---

@CADAutomation_nl wrote:

This is a familiar problem to me that I have seen more often with Vault Basic users.

In both cases when I place in a library component I also get the red dots.

When I use the Libraryeditor proj

ect file to open the file in question there seems to be nothing wrong.

So I am very curious what the possible cause is.

In the video you see how I get the files in the assembly environment, and when I open the file with the libraryeditor file

---

I have never seen this issue.

What ipj is set in Vault?

Does it act differently if the folder is not set as a library in Vault?

[CADAutomation_nl]

@BDCollett 

@arkad_s 

@CGBenner

In the video below, you can see the project mapping. I expect it has to do with that. But what is wrong is not known to me.

With normal folders it is not a problem. But this is not recommended because changes can be made accidentally. This cannot be locked in Vault Basic like in Vault professional.

[ihayesjr]

@CADAutomation_nl 

Please create a product support case for this issue.

So far, it looks like you have everything set up correctly, and this shouldn't happen.