Extract Model Properties

Extract Model Properties

Pull filtered object properties out of an already-translated design.

1. Confirm the manifest reports a successful translation before attempting to read derived data. Properties do not exist until the property database derivative has finished generating.
2. List the model views of the design and take the GUID of the first viewable, which addresses the object tree and property database for that view.
3. Retrieve the object hierarchy for the viewable. A 202 means the tree is still being generated on demand, so the step retries rather than failing.
4. Query the property database for the objects whose property matches the supplied value, returning only the requested fields. This is the scalable alternative to pulling all properties for large models.

What you'll need to have ready

• urnBase64: The URL-safe Base64 encoded URN of the source design.
• propertyKey: The property path to match on in the query (e.g. "s.props.p20d8441e" or a name path exposed by the property database).
• propertyValue: The value the property must equal for the object to be returned.
• fields: The property names to return for each matched object. Keeps large models from returning every property of every object.
• limit: Maximum number of objects to return in one page.

For your developer

Arazzo workflow autodesk:extract-model-properties, 4 operations: getManifest → getMetadata → getModelderivativeV2DesigndataByUrnMetadataByGuid → queryProperties. Specs on APIs.io.