Hello
We are using SolidWorks Enterprise PDM and when we search our vault for a "Description" property of a solidworks part, the search is correct. That is to say that the list of parts searched for is good but when the result is displayed, the "Description" column is only partially filled in while all the parts have a description.
(See attached screenshot)
Have any of you ever had this kind of problem?
Thank you for your feedback.
Jean-François BOURGINE
Hello
If it's like with us, we have to see if the info is present in @ and default. From what I was told, the result displayed corresponds to the last modification.
On our 2016 version we still have a strange operation and not in accordance with SW's specs, a Visiativ consultant has filed a request with SW to explain the behavior we are seeing today.
Basically, it randomly displays the content of @ and sometimes the content of Default, knowing that in theory there shouldn't be a discrepancy, but it happens from time to time.
Isn't it due to the fact that the description of the recording configuration must be included and it must be empty in the configuration in question?
It is possible to set it to update in all configurations in the model map editor:
Cyril F has the right answer: the properties are filled in at the file level (and appear in the @ tab) or at the configuration level (and appear at the configuration level).
The EPDM board must surely look for the "description" property either in the file property or in the configuration property but in the search display I think that only the properties of the file can appear (how to make the config property appear if a file contains dozens/hundreds of different configurations).
This seems to me to be insoluble unless you make a specific "report generator" that can generate a table with thousands of results.
You can also force the display of a variable at a given configuration. On the other hand, when you manage drawings and 3D with the same variables, it poses a problem since they are only manageable via the @ tab, the rest of the tabs are useless (no physical properties in the drawing files)
This is only valid in the vault view but not in the search view (tool limitation)
Hello everyone and thank you for these answers and this beginning of the track ;-)
I'm coming back to the subject after a few days of absence, but the display problem I'm experiencing doesn't come, in my opinion, from where my "Description" property is saved.
All my parts have a description filled in at the default configuration level.
When a part has several configurations, it is propagated to all configurations since in my data card the option "Update all configurations" is well checked, and it works very well.
None of my documents are filled in at the file level, i.e. on the @ tab.
However, when I launch a search, the display of the "Description" column is random, while the list of files found and corresponding to my search is correct...
Maybe a problem reading the database on the server, or something else but I don't see too much.
Have a nice day!
Hello
As I explained in my first answer, it may be a bug. We have the same behavior, sometimes the vault returns the contents of @ and sometimes of a configuration and this in a totally random way (some files have the right display, others don't).
Note that if propagation is enabled, it also concerns @ which should normally be autofilled because of the mapping of variables.
Unfortunately, unlike the vault view, it is not possible to force the display of the "Default" configuration in the search results.
To avoid this problem we have 'cheated' in our data cards in order to have properties exclusively linked to the file (@ tab) and others exclusively linked to the configuration (tab having a name).
The data maps are therefore quite 'cumbersome' but this is only done once EPDM is implemented. On the other hand, we end up with empty tabs in places when we try to display on the map the properties related to the configuration while we are on the @ tab (or the other way around).
So we have two sub-tabs each time and we hide (or show) the fields if the name of the tab is equal to (or different) from @.
See the attached file for user rendering on the @ tab and on a configuration tab.
As said above, see the property mapping, and the file maps to propagate properties everywhere.
This empty column problem also happens in other cases, and it is not a bug,
depending on the Copy Everywhere or Partial Mapping style settings.
and options to reset variables in the map (default).
(off-topic: the mass copying of properties is rather contrary to the basic philosophy of solidworks, for the record...)
Roughly (unless I'm mistaken) the search result shows the column, and displays the property of the last config created/update
So if we create a new part with a single config, we fill in the card, we archive, everything is fine.
Then if we re-open the file, add a config, check/fill the map, archive (initialization of variables) we end up with empty columns in the search results.
To get around this, you have to: create the new config, archive, re-extract the part, re-fill the properties / or correct the config concerned, and archive.
And then everything is ok.