Frequently Asked Questions
Why can’t I retrieve data from my models using the AEC Data Model APIs?
It is possible that your models were not successfully extracted to the AEC Data Model due to the following reasons:
- You have not yet provided us with your ACC Hub ID to be enabled to extract your models to AEC Data Model.
- Your models are not Revit 2024 models; only Revit 2024 models can be extracted into the cloud.
- Your model is still being extracted to the AEC Data Model and may take some time. The backend may have run into an error due to either an unavailable service or unhandled exceptions. In such instances, we recommend sharing the errors in your API response along with your Hub ID and Project ID.
Why do some properties return an ID as a value that I cannot resolve?
Most of the properties should be able to be resolved using referenceProperties and displayValue objects in our API. However, some properties that are enum properties are currently not supported for searching. Only “Element Context” enum property is supported for searching. For example, ‘property.name. Element Context’== Type (or Instance). This is a known limitation, and we are actively working on a solution. Please let us know where you are encountering this issue.
When will I know that my models are ready to be queried using the AEC Data Model API?
We are actively improving it and aim to offer notifications in the future. Currently, you can check the extraction status using the query aecDesignExtractionStatus
. Simply input the fileUrn
and versionNumber
from ACC Docs to see if it is in progress, successful, or failed.
How to maintain refresh tokens ?
External Databases can be used to maintain refresh tokens by implementing scheduled tasks that automatically update and refresh the tokens at regular intervals. Refresh tokens serve the purpose of obtaining new three-legged tokens without requiring users to repeat the sign in process. These refresh tokens remain valid for 14 days. In this blog. You can find an approach that uses MongoDB to store the user tokens in a collection and automate the token refresh process. For more understanding of the refresh token process, please refer to the Authentication API documentation.