PDM sanity check DB variables, custom properties ans file name references
Posted: Wed Oct 18, 2023 7:43 am
It is my memory or I am imagining things at this point. I need a sanity check on two points I assumed based on empirical experience (mine and my colleagues as well)
We have lot of custom properties that are mapped to pdm variables.
We used to change some history (version) free variable using explorer datacards without checkIng out the files. modifying the value and saving.
Today I did the same routine operation, via explorer then I opened the 3D part wih SW after modifying the datacard with exploret and the custom property inside the file did not update from the DB. Is this by design?
On the contrary the db value was nowhere and rebuilding did nothing, the OLD value was there. explorer was showing the new one.
Another "strange" thing is the update of the file references in the assemblies after a component rename: I noticed that when you open the assembly with PDM2022 the OLD references are shown until the refresh of the pdm add in or the rebuild of the assembly...
for both cases above I had in my mind that the archive server at some point would update the metadata inside the 3D files as well.
Like file deletion or cold storage is probably a batch operation that runs once a day... or so I thought.
I have also proof that some file editing happens as the pdm would show only the latest transion date instead of the date the physical file has been modified.
Thanks in advance!
We have lot of custom properties that are mapped to pdm variables.
We used to change some history (version) free variable using explorer datacards without checkIng out the files. modifying the value and saving.
Today I did the same routine operation, via explorer then I opened the 3D part wih SW after modifying the datacard with exploret and the custom property inside the file did not update from the DB. Is this by design?
On the contrary the db value was nowhere and rebuilding did nothing, the OLD value was there. explorer was showing the new one.
Another "strange" thing is the update of the file references in the assemblies after a component rename: I noticed that when you open the assembly with PDM2022 the OLD references are shown until the refresh of the pdm add in or the rebuild of the assembly...
for both cases above I had in my mind that the archive server at some point would update the metadata inside the 3D files as well.
Like file deletion or cold storage is probably a batch operation that runs once a day... or so I thought.
I have also proof that some file editing happens as the pdm would show only the latest transion date instead of the date the physical file has been modified.
Thanks in advance!