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.


Using data from custom table in features?

eric_pestyeric_pesty Member Posts: 1,632 PRO
Is there a way to "use" data from custom tables other than just "looking" at it?

It would be really nice if you could use the values in features or at least set a variable with it (instead of using a "measure" or similar feature). For example I would like to use the length of freeform splines in other features but I think the only way to do this is to create a measure value first, which seems like a waste of time as the length is already computed and shown in the table...

Is there a way to do this right now or should I submit an IR?


  • Options
    NeilCookeNeilCooke Moderator, Onshape Employees Posts: 5,519
    Tables are calculated once the feature list has been fully regenerated so you wouldn’t be able to use the results as a variable to drive features (it would create a circular reference). 
    Senior Director, Technical Services, EMEAI
  • Options
    S1monS1mon Member Posts: 2,554 PRO
    FeatureScript clearly can read from custom tables, but I don't know of a way to do this directly in Onshape, say the way you would with a variable or variable studio.

    I could see an IR for accessing a variable which happens to be an array, which happens to be in a custom table. The indices could be the text labels. 
  • Options
    eric_pestyeric_pesty Member Posts: 1,632 PRO
    Right, I guess that makes sense...
    You can see the table updates to include everything up to the rollback bar so I guess to use the data in a variable, the table would have to computed "up to that point" (as if it was rolled back just before the variable) but I guess it's a slippery slope where at some point the table would have to updated with each feature rather than just at the end to avoid circular references...

    It would be nice if there was a way to do it though but I can see how a "measure" feature is different as it has a specific place in the feature tree regen order.

Sign In or Register to comment.