Skip to main content
M
MORECREO14-Alexandrite
14-Alexandrite
April 21, 2026
Solved

Force hole callout (.hol) use internal, on existing cad geometry

  • April 21, 2026
  • 2 replies
  • 61 views

hole_file_resolution use internal

 

How do I updated old files so that any hole callout they are using is saved internally, without going back through every part and updating every hole callout?

 

Up till now, cad files have not been saving .hol files internally.

The .hol files have since been updated to include default_callout_format_data. (which allowed me to combine multiple files into one)

So using the same file names on .hol callouts wont work, because I was able to reduce the total number required.

The main issue, now when I go to put in a hole, there are multiple ‘Thread Type’ selections and half of them will be unused going forward.

But if I remove them, old files will contain incomplete hole callouts due to the ‘hole_file_resolution use internal’ not being set when the part was created.

Hiding the old .hol files so they can still be read but are not displayed would be acceptable as well, but I’m not seeing any options for that.

Any suggestions on how to use the new .hol files without watering down the ‘Thread type’ dropdown with outdated options would be much appreciated.

 

Thank you!

Best answer by DB@HuscoInt

One option would be to switch hole_file_resolution back to external, which is the default behavior.

This is generally why it's important to finalize your custom thread table names before changing the configuration to internal. Once the hole data is stored internally, renaming or consolidating .hol files becomes much more difficult because existing models retain references to the original data.

If you keep the setting as external and change the hole table filename, Creo will resolve the hole definition from the external .hol file. For any hole that cannot find an exact match, the callout will typically default to the first hole definition in the first hole chart found alphabetically. Because of that, you'll want to thoroughly test any filename or table changes before rolling them out.

Unfortunately, there isn't a simple bulk method to update all existing parts so their hole callouts are resaved internally with the new .hol definitions. In most cases, you're choosing between:

  • Keeping the legacy .hol files available so older models continue to resolve correctly.
  • Updating and resaving affected models to embed the new hole definitions.
  • Reverting to external resolution and managing the thread tables centrally.

If your goal is simply to remove obsolete thread types from the dropdown while maintaining compatibility with older models, keeping the legacy .hol files available (but separated from the active standards if possible) is usually the safest approach.

2 replies

A
anursinghCommunity Manager
Community Moderator
June 1, 2026

Hi ​@MORECREO,

Thank you for your question. 

Your post appears well documented but has not yet received any response. I am replying to raise awareness. Hopefully, another community member will be able to help.

Also, feel free to add any additional information you think might be relevant. It sometimes helps to have screenshots to better understand what you are trying to do. 

 

Regards,

Anurag 

DB@HuscoInt
DB@HuscoInt12-AmethystAnswer
12-Amethyst
June 5, 2026

One option would be to switch hole_file_resolution back to external, which is the default behavior.

This is generally why it's important to finalize your custom thread table names before changing the configuration to internal. Once the hole data is stored internally, renaming or consolidating .hol files becomes much more difficult because existing models retain references to the original data.

If you keep the setting as external and change the hole table filename, Creo will resolve the hole definition from the external .hol file. For any hole that cannot find an exact match, the callout will typically default to the first hole definition in the first hole chart found alphabetically. Because of that, you'll want to thoroughly test any filename or table changes before rolling them out.

Unfortunately, there isn't a simple bulk method to update all existing parts so their hole callouts are resaved internally with the new .hol definitions. In most cases, you're choosing between:

  • Keeping the legacy .hol files available so older models continue to resolve correctly.
  • Updating and resaving affected models to embed the new hole definitions.
  • Reverting to external resolution and managing the thread tables centrally.

If your goal is simply to remove obsolete thread types from the dropdown while maintaining compatibility with older models, keeping the legacy .hol files available (but separated from the active standards if possible) is usually the safest approach.

    Terms & ConditionsAccessibility statement