Inputs
FindAssetsInput
Input fields for the Assets query. Assets can be filtered by an array of IDs (assetIds field) or by an RSQL or query object filter (filter field), but not both. Either assetIds or projectId can be specified, but not both.
Fields
| filter | Filters applied to the query. Filters are an RSQL string or a JSON query object. See “Filters” in the Flow Data API Developer Guide for a more complete description of these formats. Example queries are: - “filter”: “attribute.name==’asset alpha’” (find all assets with a specific name, case-sensitive). - “filter”: “attribute.description=like=*descr*” (find all assets with a description containing “descr”, case-insensitive). - “filter”: “attribute.version>0” (find all assets with a last version greater than 0). - “filter”: “attribute.id=like=’*3Y*’” (find all assets with an ide that contains “3Y”). - “filter”: “components.typeId==autodesk.data.l2fs:components.link-1.0.0” (find all assets with at least one component of these types). A query using only “attribute.storageKey==” is ‘optimized’ for performance, as it uses an index to find the object directly without iterating over a list. A query using only “has.component.type” will use closure query semantics, and will stop when reaching an asset that doesn’t match this field. Use “components.typeId” if this is not desired. All other queries will iterate through all the assets under the project and perform the comparisons client-side. Providing an empty string (“”) or an empty object ({}) is equivalent to providing null or no filters, and will not filter the result set. |
| projectId | projectId is optional but required if filter is provided. You cannot specify both projectId and assetIds. If only projectId is provided the assets query returns an array of assets belonging the given projectId. |
| rootAssetId | A specific asset in the graph to start the search from. Cannot be used in conjunction with assetIds and projectId. Please note that the asset you start from will not be included in the resulting data set. |
| depth | This parameter regulates the number of layers that are used during the asset graph traversal. The default value is 0, which means that the whole graph from the given root will be scanned. If `depth ` equals 2, that means that only two immediate levels will be explored. |
| pagination | Allows pagination of results. Note that when assetIds is provided this field is ignored |
Where Used
| Usage | Used By | Description |
|---|---|---|
| Argument for Query | assets | Get assets under a project by filters |
