Skip to main content
T
TP_98623739-Granite
9-Granite
October 16, 2025
Solved

Batch drawing changes using map key and dbatch

  • October 16, 2025
  • 3 replies
  • 860 views

Hi,

I have 100 part numbers , in which the drawing has to be opened from windchill into creo session and it should run a particular already recorded map key then it should save back into the workspace or windchill check in , When i tried running the dbatch program in native creo, it says license error. 

My company has customized tools inside creo and its based on floating license i guess. So is there any ways i can link that creo to the dbatch script or i should go with toolkit api commands or trail_file based scripting ?

Does these methods other than dbatch have option to run in background or while the system is ideal (after working hours or scheduled time).  

 

Best answer by remy

Hi

the most comprehensive article about dbatch is this one : https://www.ptc.com/en/support/article/CS139340

pay specific attention to the known limitations section.
Recently the memory management for large model is also a limitation that has been hit.

All in all i recommend that you follow the recommendation to explore and consider the creation of a custom script-based tooling alternative.

If your company can deliver, invest in Creo Toolkit and create your own batch tool else you can ask a partner.

3 replies

M
MartinHanak24-Ruby III
24-Ruby III
October 17, 2025

Hi,

If you are familiar with trail files then you can generate and play trail file instead of running dbatch.

    R
    RPN18-Opal
    18-Opal
    October 17, 2025

    If you open a piping assembly without having the license, no worry as long you don’t try to modify. I have no clue what your mapkey is doing, but I would invest time to configure the right psf file for the right license. A mapkey or trail file will execute like a recorder. This is not the same like open and print!

    R
    remy21-Topaz IAnswer
    21-Topaz I
    October 22, 2025

    Hi

    the most comprehensive article about dbatch is this one : https://www.ptc.com/en/support/article/CS139340

    pay specific attention to the known limitations section.
    Recently the memory management for large model is also a limitation that has been hit.

    All in all i recommend that you follow the recommendation to explore and consider the creation of a custom script-based tooling alternative.

    If your company can deliver, invest in Creo Toolkit and create your own batch tool else you can ask a partner.

    Terms & ConditionsCookie settingsAccessibility statement