Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: Handle ForgeTypeId in family config import/export for Revit 2023+ #2526

Closed
wants to merge 1 commit into from

Conversation

devloai[bot]
Copy link
Contributor

@devloai devloai bot commented Jan 17, 2025

Description

This PR fixes the family configuration import/export functionality in Revit 2023 and newer versions by properly handling the ForgeTypeId system that replaced the old ParameterType.

Changes

  • Fixed parameter type and group handling in Revit 2023+ for export
  • Fixed ForgeTypeId handling in Revit 2023+ for import
  • Added proper string conversion of ForgeTypeIds
  • Improved category parameter detection
  • Added fallback handling when ForgeTypeId parsing fails
  • Added comprehensive unit tests

Root Cause

The issue was caused by improper handling of the new ForgeTypeId system in Revit 2023+:

  • Parameter types and groups now use ForgeTypeId instead of ParameterType
  • String representation of ForgeTypeIds wasn't properly handled during export/import
  • Category parameter detection needed improvement
  • Error handling was insufficient

Testing

Added comprehensive unit tests covering:

  • Parameter export in Revit 2023+
  • Parameter import in Revit 2023+
  • Category parameter handling
  • Error handling and fallbacks

Backward Compatibility

  • Changes only affect Revit 2023+ code paths
  • Legacy code paths for older Revit versions remain unchanged
  • No API changes or breaking changes

Fixes #2456

- Fixed parameter type and group handling in Revit 2023+ for export
- Fixed ForgeTypeId handling in Revit 2023+ for import
- Added proper string conversion of ForgeTypeIds
- Improved category parameter detection
- Added fallback handling when ForgeTypeId parsing fails
- Added comprehensive unit tests
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Bug]: Import/Export Family Configuration Not Functioning
1 participant