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.

Building a basic Custom Properties Custom Table....problems...

john_allen289john_allen289 Member Posts: 8 PRO
Hi,

I'm trying to build the most basic Custom Table to show a custom propery of a selected part within the Part Studio. I've butchered the Part Masses sample Custom Table to get this far

Started small, just 1 column 1 row to pull in one custom property, but my precondition to be able to select a part for the custom table is not working, error showing not compatible with Table, but I can see in the FSDocs an optional query of entities for Tables is there, but really not sure how to utilize this outside a precondition? Any thoughts. Thanks all.




Best Answer

  • NeilCookeNeilCooke Moderator, Onshape Employees Posts: 3,691
    Accepted Answer
    The precondition for a table is to set parameter defaults (for example) in the table - it does not work with queries. You could cycle through all the parts in the Part Studio and create a separate table for each, but if there are a lot of parts your tables could get very long.
    Director, Technical Services, EMEAI

Answers

  • NeilCookeNeilCooke Moderator, Onshape Employees Posts: 3,691
    Accepted Answer
    The precondition for a table is to set parameter defaults (for example) in the table - it does not work with queries. You could cycle through all the parts in the Part Studio and create a separate table for each, but if there are a lot of parts your tables could get very long.
    Director, Technical Services, EMEAI
  • john_allen289john_allen289 Member Posts: 8 PRO
    Hi Neil, thanks for clarifying that limitation, understood. Agree the custom table could get pretty long, but I'm planning to export the table to excel, so size isn't a major issue, so if I added a Part Name column I could filter this out in an excel query for the Part in quetsion, then paste this data back into a drawing table to create drawing notes that are derived from the Part Studio Custom Properties (that's where I'm ultimately heading with this), Does this seem achievable?

    Also, can you help explain how to apply the optional 'entities is Query' TYPE, and what this does? I couldn't find a custom table sample that used this as a reference case, didn't know if this might help extract specific Part data?

    Thanks for your time as always.
Sign In or Register to comment.