Known Issues
This page documents known issues and limitations with the Manufacturing Data API that may affect your application development. We recommend reviewing these before implementing your solution.
Note: This list is updated regularly as issues are discovered and resolved. Check back periodically for the latest information.
Search Limitations
Files and Folders Require Explicit Inclusion
- Issue: Files and Folders are only returned in search results when explicitly included in
desiredSearchResultTypes. By default, only Components and Models are returned. - Impact: Search queries may appear to miss Files and Folders unless they are explicitly requested.
- Status: This behavior is planned to be fixed in a future release.
Custom Properties Limitations
The following limitations affect custom properties functionality:
File Import/Export Limitations
- Issue: Custom properties are not preserved during design file export and import operations
- Impact: Custom property data is lost when transferring files between systems
- Workaround: Use the API to retrieve and reapply custom properties after file operations
Domain Events
Misspelled Field in component.primary.updated Payload
- Issue: The
component.primary.updatedevent payload emits the fieldpreivousPrimaryModelIdinstead of the intendedpreviousPrimaryModelIddue to a typo in the implementation. - Impact: Applications that reference
previousPrimaryModelIdwhen handling this event will not find the field. The payload currently contains onlypreivousPrimaryModelId. - Workaround: Read the field as
preivousPrimaryModelIduntil the fix is released. - Status: This will be corrected in a future release. The field name in the payload will change to
previousPrimaryModelIdwhen resolved.
Component
Deprecation Reason for isStandalone References an Unavailable Field
- Issue: The deprecation reason for
Component.isStandalonedirects you to useComponent.type, which is not yet available in the public API. - Impact: Queries that request
Component.typewill fail validation. TheisStandalonefield remains available and functional. - Workaround: Continue using
isStandaloneuntilComponent.typeis released.isStandalonereturnstrueonly when the component has exactly one design, andfalsewhen it has no designs (non-CAD or orphan components) or several designs (Shared Part Number). - Status:
Component.typeis planned for an upcoming release. This entry will be removed once it is available.
Integration and Development Considerations
API Version Compatibility
- Ensure your application handles API version updates gracefully
- Test thoroughly when migrating between API versions (e.g., v2 to v3)
Rate Limiting
- Be aware of API rate limits when making bulk operations
- Implement proper retry logic and error handling
Getting Help
If you encounter issues not listed here:
- Review Error Handling for error resolution strategies
- Contact Autodesk Developer Support for additional assistance