Welcome to the Onshape forum! Ask questions and join in the discussions about everything Onshape.
First time visiting? Here are some places to start:- Looking for a certain topic? Check out the categories filter or use Search (upper right).
- Need support? Ask a question to our Community Support category.
- Please submit support tickets for bugs but you can request improvements in the Product Feedback category.
- Be respectful, on topic and if you see a problem, Flag it.
If you would like to contact our Community Manager personally, feel free to send a private message or an email.
Will we ever be able to getProperties() during regen?
Might be a questions for @ilya_baran or @lana.
I know it's a current limitation that getProperty() only works in things after feature regeneration like Custom Tables and apparently Editing Logic. I believe it's regen order that means the properties "don't exist" until after the features regen. Do I have that right? In any case, my question is will this ever change? The more teams I work with the clearer it is that data wrangling is as big or a bigger challenge than just modeling things, and there are a lot of data challenges that could be solved by access to part properties during feature regen.
In a similar vein, is it on the road map to be able to set previously un-set properties without having to "Reset all"? It would certainly make for a more streamlined and intuitive experience.
Are these too architecturally fundamental to hope for these changes?
Best Answer
-
ilya_baran
Onshape Employees, Developers, HDM Posts: 1,237 
Makes sense. The changes involved would be pretty fundamental, but we've been kicking around some ideas that could change (among other things) how this works. Now, if something comes of it, it's still years out.
Ilya Baran \ VP, Architecture and FeatureScript \ Onshape Inc4
Answers
+1 to this being a bit of pain.
How do you handle the corner cases like changing a property in a versioned part studio? Versioned documents shouldn't change, but changing a property would have to trigger regen?
setproperty should take in a parameter for "override user set property" to allow us to always set a property - even if the user manually changed it at some point. One of the benefits of FeatureScript is to enforce standards. But allowing a user to supersede that standards enforcement limits its value.
I know that a user could change it, and regen will have to happen for it to be applied again, but thats better than what we currently have.
Custom FeatureScript and Onshape Integrated Applications
+1
Learn more about the Gospel of Christ ( Here )
CADSharp - We make custom features and integrated Onshape apps! Learn How to FeatureScript Here 🔴
Makes sense. The changes involved would be pretty fundamental, but we've been kicking around some ideas that could change (among other things) how this works. Now, if something comes of it, it's still years out.
Thanks, Ilya. I assumed it was fairly fundamental, but I would love to see something like this on the roadmap. No clue if the scale of the challenge is similar, but it makes me remember how variables in sketch patterns weren't possible for so long because of some non-trivial challenges, and it got done eventually (and I use it a lot now). I'd love to be part of an EVP for it whenever that is.
The Onsherpa | Reach peak Onshape productivity
www.theonsherpa.com
+1
chadstoltzfus@premiercb.com