Learning Forum

[julian.schlueter]

Hi, I was trying to set up a shared material library so that every user would have access to the same materials and properties. 

I've found the option to set the path and copied a "MaterialLibrary.xml" file in that foulder.

Unfortunately Discovery is giving me an error, stating that the "data was not formatted correctly".

I couldn't find any documentation on this and since our users haven't got admin rights, replacing the original library on C: isn't an option.

 

We are using Discovery 2021 R2.

 

Many thanks in advance and kind regards

Julian

[Subashni Ravichandran]

Hello J. Schlüter

Let me check from my end and get back to you on this. 

[Subashni Ravichandran]

Hello J. Schlüter

Please check this page in the help document. Please let me know if you have tried this?

[julian.schlueter]

Hello Subashni 

Thanks for your investigation, I have seen this topic in the help document. The way I understand material libraries in Discovery however is that you are able to provide a shared material library (let's say on a network folder) and point to this folder in the settings. All users will then have the same materials. 
The mentioned "User Defined Material Libraries" will be used if a user changes some properties of a shared material and saves his copy in his own User Defined Material Library.
I've tried this and it creates a MyLocalMaterialLibrary.json file. Maybe there is a way to rename this to "shared..." and save it to the predefined folder as shared library? But then again Discovery tries to read a XML-file, so maybe the shared library should still be a XML- and noch JSON-file?
It would be nice if someone could give us a hint on the expected file name and format. 

Have a nice Weekend!

Kind regards

Julian

[Subashni Ravichandran]

Hello J. Schlüter

Every time Discovery is launched Discovery looks for that specific file from the specific location to load the materials for each session. 

Unfortunately, the material library cannot be moved to a shared location for Discovery to find.
The current workaround would be to copy the .json file each time it is updated and share it manually with other users and request them to replace the .json file in the specified location on theri individual machine. 

I will take this feedback to my team and check if there is anything that can be done here.