Hello, I'm going back to a problem of pre-populating MS body properties from libraries. We create mechanically welded PRTs using the MS bodies and their properties to make plans of each flow rate and bill of materials for purchases. These MS bodies are created in 3 ways: 1- Classical functions (extrusion, material removal, drilling) for laser-type flow rates. There can also be sheet metal functions for parts made by laser+bending 2- " Mechanically welded element" functions for all H, I, etc. They are made from the sldlfp files 3- Functions via the Design Library for functions grouped together in the library.
So we create the PRT in 3D and fill in the properties of the MS bodies with Smart Properties For the 1st case, we have to fill everything in each time. Normal, we create from " nothing "
For the 2nd case, the configs of the sldlfp files contain properties that will be automatically found in the MS body, that's tip-top! ==> and via the Smart, we see this:
On the other hand, for the 3rd case, I can't bring up any property... ==> and it's empty, the fields are not created until the SMart has gone through
In the construction tree of the room, I have my MS bodies that are created from the corresponding functions
Hello; This seems to me to be a normal behavior of Smartproperties, it prefers to write properties rather than read them. And unless the properties are already included in your document templates (the properties, not the values) it is normal that, without launching the Smartproperties, they are not created in your Solidworks documents...
Be careful in the 2nd case Description (for the welded mechanic) in the 3rd DESCRIPTION (for the function) for Smartproperties it's not the same thing (And in the smartpropertie (DESCRIPTION). Wouldn't your problem come from there? Otherwise we don't see how you get the Description property of the mechanically welded in your DESCRIPTION property of the smart.
Hello, Thank you for your reactions I would like to point out that: In case 2, the sldlfp file that contains the sketch of the profiles has in its properties (linked to the config) the properties shown in the view: Description (HEA100), Standard (NF EN...), and MODE_OBTENTION. When using the " MS Element" function, the MS body that is created automatically contains the Description, Standard, and MODE_OBT.) and they are filled with the corresponding values. the Smart only rereads these values and you can enter the other values: REPMS, the choice if plan or not, etc
and SW doesn't differentiate between an uppercase or lowercase property name
