Welcome to the Onshape forum! Ask questions and join in the discussions about everything Onshape.

First time visiting? Here are some places to start:
  1. Looking for a certain topic? Check out the categories filter or use Search (upper right).
  2. Need support? Ask a question to our Community Support category.
  3. Please submit support tickets for bugs but you can request improvements in the Product Feedback category.
  4. 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.

USE DERIVE FEATURE TO DERIVE PART STUDIO VARIABLES

shawn_crockershawn_crocker Member, OS Professional Posts: 869 PRO
I was just thinking it would be very useful to be able to use the derive feature to also derive part studio variables in to another part studio.  In my case, I often have a configured master part studio.  I then derive parts from the master into other studios.  I usually also configure the single part studio to drive the derived features configuration inputs.  If I was able to derive certain variables in along with the part like we currently can with sketches and planes, I would be able to perform addition work on the derived part using the logic that came in with the derived variable.  If we can derive sketches and planes, why stop the derive feature there.  Why not allow deriving of variables?  All this talk of global variables.  This could sort of work just like global variables.
Tagged:

Comments

  • shawn_crockershawn_crocker Member, OS Professional Posts: 869 PRO
    @CBowers
    Thanks so much!  I completely assumed for some reason deriving variables would be out of bounds of featurescript.
  • shawn_crockershawn_crocker Member, OS Professional Posts: 869 PRO
    @CBowers
    I'm unsure how this feature works.  I don't seem to be getting the variables coming in.  I have checked the box and assigned a prefix but no variables are coming through.
  • ilya_baranilya_baran Onshape Employees, Developers, HDM Posts: 1,215
    @shawn_crocker If you share a link to a public document where super-derive isn't working, I can try to diagnose.
    Ilya Baran \ VP, Architecture and FeatureScript \ Onshape Inc
  • shawn_crockershawn_crocker Member, OS Professional Posts: 869 PRO
    @ilya_baran
    Thanks for the response.  In creating a sample document I discovered it was working.  I think in my original attempt I may has accidentally included a space in the prefix or something.
  • ilya_baranilya_baran Onshape Employees, Developers, HDM Posts: 1,215
    Good point: I just updated super-derive so it will report an error if the prefix or suffix is invalid.
    Ilya Baran \ VP, Architecture and FeatureScript \ Onshape Inc
  • shawn_crockershawn_crocker Member, OS Professional Posts: 869 PRO
    Thanks for that.  
  • ValNthValNth Member Posts: 4

    Sorry to bother on an older thread like this, but I'm not quite sure how to derive variables with SuperDerive. I have no programming background and I attempted to use every variable prefix and suffix I could look up, but I couldn't figure out, on what basis I should name them in the SuperDerive feature to get access to my variables. Could you perhaps break there use down for me a bit in this context, I'd really appreciate the helping hand.

  • shawn_crockershawn_crocker Member, OS Professional Posts: 869 PRO

    @ValNth As for as I remember, you don't actually have to use the preffix or suffix. You only need to use them if you know the studio you are deriving them into already contains variables that might be named the same as in the studio you are deriving from. So, I think all you need to do is include the variable and they come in as the same name as they were in the parent studio.

  • ValNthValNth Member Posts: 4

    Thank you for the help! Turns out the problem was simpler than I expected.
    First off, I simply assumed that super derive lets me select the created variables as entities to be derived and it didn't occure to me, that I just have to derive the studio and the variables will be there in the background automatically.
    After that I just struggled a bit, because the exact ones I needed didn't appear, but after a good 20 minutes I realized, I just forgot to save a new version of the desired part studio, since I created those variables.
    Couple of rookie mistakes, but now everything works as it's supposed to, so thank you once again!

Sign In or Register to comment.