KB: Component Release and Creation Errors Caused by HRID Generation Failures

A365 A365
Users may encounter component creation or release failures when Altium cannot generate a valid Hierarchical Revision ID (HRID). This commonly occurs when a component template enforces a naming scheme that conflicts with the folder-level naming scheme, or when the available HRID range is exhausted due to a limited numbering pattern. Updating the template naming scheme, enabling override behavior, verifying folder naming settings, expanding the numeric range, and preserving lifecycle states during synchronization resolves the issue and helps prevent future HRID generation failures.

At a Glance

Users may encounter component creation or release failures when Altium cannot generate a valid Hierarchical Revision ID (HRID). This commonly occurs when a component template enforces a naming scheme that conflicts with the folder-level naming scheme, or when the available HRID range is exhausted due to a limited numbering pattern. Updating the template naming scheme, enabling override behavior, verifying folder naming settings, expanding the numeric range, and preserving lifecycle states during synchronization resolves the issue and helps prevent future HRID generation failures.
Go Deeper with AI:

Solution Details

Component Creation or Release Fails with HRID Error

When creating or releasing a component, Altium displays the following error:

Failed to generate HRID for content type=altium-component folder=BBXXXXXX naming scheme=$CONTENT_TYPE_CODE-000-{0000}.

Single Component Editor error dialog stating: 'Failed to generate hrid for content type altium-component folder B8AD5A22-999E-48CD-AE3F-4085EE09F5F1; naming scheme $CONTENT_TYPE_CODE-000-{0000}

The error prevents new components from being created or synchronized correctly within the workspace.

Template and Folder Naming Schemes Conflict

Altium uses naming schemes to generate unique HRIDs. While folder-level naming schemes typically define the HRID format, components created from templates inherit the naming scheme configured within the template. If Allow override is disabled, the folder-level naming scheme is ignored and conflicting or outdated rules may be applied.

Additionally, a numeric pattern such as {0000} provides a limited pool of available IDs. Once that range is exhausted, Altium cannot generate additional HRIDs.

Required Configuration Changes

  • Update the HRID naming scheme in the component template.
  • Increase the numeric block from {0000} to {00000}.
  • Enable Allow override in the template.
  • Verify the destination folder's naming scheme.
  • Enable Preserve lifecycle state during batch updates and synchronization.
  • Review synchronization mappings and use Item mappings where lifecycle preservation is required.
  • Apply consistent configuration changes across all related templates.

Update Template Settings and Validate HRID Generation

  1. Open the Component Template

    1. Navigate to Tools » Data Management » Component Templates.
    2. Open the template used for the affected component type.
  2. Update the Naming Scheme

    1. Locate the Component Naming Scheme field.
    2. Update the naming scheme to match the workspace standard.
    3. Change the numeric block from {0000} to {00000}.
    4. Save the template.
  3. Enable Allow Override

    1. Open the template's Component Options.
    2. Enable Allow override.
    3. Save the changes.
  4. Verify the Folder Naming Scheme

    1. Open the destination component folder.
    2. Review the configured Item Naming Scheme.
    3. Confirm that the format matches the intended HRID standard and provides sufficient numbering capacity.
    4. Update the folder naming scheme if necessary.
  5. Apply Changes to Related Templates

    1. Repeat the naming scheme and override updates for all templates that use the same HRID logic.
    2. Verify consistency across all component templates.
  6. Preserve Lifecycle State During Synchronization

    1. Open the Batch Component Editor.
    2. Enable Preserve lifecycle state.
    3. If using PLM synchronization, review parameter mappings and use Item mappings when lifecycle state preservation is required.
    4. Proceed with the synchronization or release.
  7. Validate the Resolution

    1. Create a new component and confirm that HRID generation succeeds.
    2. Synchronize existing components and verify that naming and lifecycle settings are retained.
    3. Confirm that newly created components receive HRIDs based on the expected naming scheme.

Additional Notes

  • HRID failures commonly occur when naming-scheme capacity is exhausted or when conflicting naming rules exist between templates and folders.
  • Expanding the numeric block to {00000} significantly increases the available HRID range.
  • Users working with locally cached templates may need to refresh or re-download updated templates.
  • If the issue persists after updating naming schemes, verify that the requested Item ID is not already reserved by an existing or previously abandoned item.

References

If you find an issue, select the text/image and pressCtrl + Enterto send us your feedback.