Set a custom property via Featuresript for another custom property

graeme_anderson

I am currently trying to write a bit of featurescript that will query a manual entry custom property within a part and write it to another custom property in a drawing.

The part custom property has an ID that I can access, but I am really struggling to get the syntax right. Can anyone point me at an example of this?

MichaelPascoe

You don't need to call getProperty in order to use setProperty. In fact, getProperty is pretty difficult to use because Onshape doesn't get the property until the entire feature has been built, that is my understanding anyways. If you do need to use getProperty, here is how you can do it: getProperty - forum post

MichaelPascoe

Yeah, when getting properties, it only updates if you open up the feature due to the current limitations. Here is an improvement request you can vote on if you like: getProperty in FeatureScript - Improvement request

MichaelPascoe

@graeme_anderson, once you create your custom property, it should have an ID. You can use that ID like this to set it within a custom feature. Setting a custom property is slightly different than setting a normal property, see the example below:

//Set the part to "Not revision managed" and "Exclude from BOM"

    setProperty(context, {
                "entities" : bodyQuery,
                "propertyType" : PropertyType.CUSTOM,
                "customPropertyId" : "57f3fb8efa3416c06701d61d",
                "value" : "true"
            });

    setProperty(context, {
                "entities" : bodyQuery,
                "propertyType" : PropertyType.EXCLUDE_FROM_BOM,
                "value" : true
            });

graeme_anderson

Thanks for your response @MichaelPascoe.

One further question: do I have to call getProperty prior to calling setProperty or is propertyType.CUSTOM enough?

MichaelPascoe

You don't need to call getProperty in order to use setProperty. In fact, getProperty is pretty difficult to use because Onshape doesn't get the property until the entire feature has been built, that is my understanding anyways. If you do need to use getProperty, here is how you can do it: getProperty - forum post

graeme_anderson

@MichaelPascoe thanks for the insight and the pointers. I don't think I can get featurescript to do what I need it to do, due to the limitations of getProperty in that case.

MichaelPascoe

Yeah, when getting properties, it only updates if you open up the feature due to the current limitations. Here is an improvement request you can vote on if you like: getProperty in FeatureScript - Improvement request