• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Allegro X PCB Editor
  3. Accessing user defined Properties in Documentation Editor...

Stats

  • State Verified Answer
  • Replies 5
  • Subscribers 168
  • Views 915
  • Members are here 0
More Content

Accessing user defined Properties in Documentation Editor Templates

Electro Node
Electro Node 2 months ago

Hello All,

I have created some user‑defined properties on components in PCB Editor. While generating APP data using the Documentation Editor, I can see all the standard component properties in the template, but the user‑defined properties do not appear.

Is there a specific setup, configuration, or property‑mapping step required to make user‑defined component properties available in the Documentation Editor templates in assembly documents?

Best Regards,

  • Cancel
  • Sign in to reply
Parents
  • CJ202604307615
    0 CJ202604307615 1 month ago

    This usually happens when user-defined properties aren’t mapped or exposed to the documentation layer. Try checking if those properties are marked for export or included in the template configuration. Also, verify naming consistency and scope, sometimes only specific property sets are picked up by default.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • Electro Node
    0 Electro Node 1 month ago in reply to CJ202604307615

    Hi CJ202604307615,

    Thanks for the suggestion and your input on this.

    I have checked, and the solution suggested by LogicNet LogicNet works well here. I believe the documentation editor considers the properties from IPC-2581. The properties defined while exporting IPC-2581 are taken into account by the documentation editor.

    Although the properties are visible in Allegro and work fine, they are not reflected unless we add those properties to IPC-2581 export. So, I tried the suggested solution, and it worked for meSlight smile.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
Reply
  • Electro Node
    0 Electro Node 1 month ago in reply to CJ202604307615

    Hi CJ202604307615,

    Thanks for the suggestion and your input on this.

    I have checked, and the solution suggested by LogicNet LogicNet works well here. I believe the documentation editor considers the properties from IPC-2581. The properties defined while exporting IPC-2581 are taken into account by the documentation editor.

    Although the properties are visible in Allegro and work fine, they are not reflected unless we add those properties to IPC-2581 export. So, I tried the suggested solution, and it worked for meSlight smile.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
Children
No Data
Cadence Guidelines

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.

© 2026 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information