Taking the reply from @Gerco as an occassion to to share some experience.
We are aiming at a live experience. When we publish new ito,s classifications etc we would like them to be available to all users instantly.
Being able to use relative paths or are sharepoint location in the resource root path would already save a lot. Maybe one of the @Solibrians can shed some light on relative paths?
Totally agree users need to understand when to use a new company standard or use the ones already available on the current project. It’s part of our company training but to make sure our company standards are “hufterproof” they are on a read-only location. Just to be save. Project specific changes of our standards are saved to the project folders.
This is basically the use case for most organisations I guess and from my experience a dedicated server location which is accessible for all but at the same only writteable for few works best - but it also requires the infrastructure and is less flexible.
Recently working with a shared OneDrive/Sharepoint location leaves behind some mixed feelings as syncing in the background to keep users up to date is somehow not always working as expected.
Actually if new files are getting deployed to the shared location and even sync settings for this location are set to “Keep always available” it seems like that this is causing issues as Solibri often throws the usual file reading error before all the ressources could be loaded.
Not sure why this is happening, but if it does it is pretty annyoing as then I have to either force close or dismiss tons of warnings to proceed.
6fe3a94f-3f0e-41f0-ab62-316de741732c-image.png
And then there is the “hufterproof” point, which is something where a seperation of test, developement and productive environments for ressources gets more complicated as it should be causing the need for third party services to reduce time for administration.
So to sum it up, still have not found a best practice workflow which satisfies the needs and is easy at use at the same time but probably there are already better ways to achieve what’s needed but I just don’t know enough about deployment.