Part Naming

cory_isaacson

I am using FS to generate multiple parts in a single feature (sometimes 20 or more). They come out with default names, like Part1, Part2, etc. I understand that part naming is not possible right now with FS. Is there a way to do this with the API, after the parts are generated? If so, how can I figure out what PartN is so I can rename it (such as MyPartN)?

kevin_o_toole_1

Yep, we definitely want a pure FS solution for naming an other metadata in the future.

For now the process will involve the following steps:

1. (optional, might make querying easier later) In FeatureScript, call setAttribute on a part created with an attribute of e.g. { "myPart" : "top" } or { "myPart" : "side" ~ i }
2. In the API, get deterministic ids for specific parts. This will involve calling Part Studios: Evaluate FeatureScript API with a function returning transientQueriesToStrings(evaluateQuery(someQuery))), where someQuery is either:
   • A query for the specific part you want (possibly a qCreatedBy("someOperation", EntityType.BODY)), OR
   • If you did step 1, a qAttributeFilter for the specific attribute (e.g. { "myPart" : "top" }) set for the part in step 1
3. Use the Parts: Update Metadata API (or, for multiple parts, the Parts: Update Part Metadata API) to set the name of a Part based on its deterministic id.

I sure you can see why we really want a pure FeatureScript solution

In the meantime, let us know if you encounter any issues with the strategy outlined above! 

kevin_o_toole_1

Yep, we definitely want a pure FS solution for naming an other metadata in the future.

For now the process will involve the following steps:

1. (optional, might make querying easier later) In FeatureScript, call setAttribute on a part created with an attribute of e.g. { "myPart" : "top" } or { "myPart" : "side" ~ i }
2. In the API, get deterministic ids for specific parts. This will involve calling Part Studios: Evaluate FeatureScript API with a function returning transientQueriesToStrings(evaluateQuery(someQuery))), where someQuery is either:
   • A query for the specific part you want (possibly a qCreatedBy("someOperation", EntityType.BODY)), OR
   • If you did step 1, a qAttributeFilter for the specific attribute (e.g. { "myPart" : "top" }) set for the part in step 1
3. Use the Parts: Update Metadata API (or, for multiple parts, the Parts: Update Part Metadata API) to set the name of a Part based on its deterministic id.

I sure you can see why we really want a pure FeatureScript solution

In the meantime, let us know if you encounter any issues with the strategy outlined above! 

adamohern

Is this still the state of the art? Is there an FS solution yet?

ilya_baran

There is no FS solution yet, but we are closer -- a number of changes are in the works, that when combined, will make it possible to set part names and colors in FS.

john_hanson

Bumping this thread. Is this still the best way? Very much looking forward to a FS solution.

ilya_baran

The state is still unchanged but we're very close to releasing this ability.