FAQ
- How can I contact Autodesk Support?
- Does Data Exchange - Dynamo Connector support only the English language?
- Is Data Exchange a file?
- Why does Data Exchange have a size of zero in Autodesk Docs?
- How can I remove a Data Exchange - Dynamo Connector plug-in?
- Does Data Exchange support material mapping?
- Why do I need to host Data Exchanges in Autodesk Docs even though I can create them with the Revit Connector on my computer?
- What should I know if the source file is shared, saved as, or copied?
How can I contact Autodesk Support?
You can reach us through the following communication channels:
Does Data Exchange - Dynamo Connector support only the English language?
Yes, Data Exchange - Dynamo Connector supports the English language only.
Is Data Exchange a file?
Data Exchanges are not files.
Why does Data Exchange have a size of zero in Autodesk Docs?
The Data Exchange files in Autodesk Docs or BIM 360 serve only as references and do not contain any data. They point to the Data Exchange information that is stored at a granular level.
How can I remove a Data Exchange - Dynamo Connector plug-in?
Uninstall the Data Exchange - Dynamo Connector from the control panel. For more information, see the Uninstall topic.
Does Data Exchange support material mapping?
Currently, Data Exchange elements only retain the color of the elements. Data Exchange does not support material mapping and render styles.
Why do I need to host Data Exchanges in Autodesk Docs even though I can create them with the Revit Connector on my computer?
They are hosted in a Cloud object storage to allow collaboration among team members across various disciplines. They also allow your app to use services, download data from the broader Autodesk Platform Services ecosystem, and exchange information using various tools such as 3D applications, spreadsheet processors, and databases.
What should I know if the source file is shared, saved as, or copied?
When a source file such as a Revit, Rhino, or Inventor is shared with others and saved under a new name, or copied to a different location or project, it can result in multiple file versions linked to the same exchange. This may lead to accidental updates from different versions, causing confusion and version conflicts. To prevent this, avoid updating an existing Data Exchange from any shared, renamed, or copied file. Instead, create a new Data Exchange when working with such files to ensure version clarity and avoid conflicts.
