Community Tip - When posting, your subject should be specific and summarize your question. Here are some additional tips on asking a great question. X
Good afternoon,
I've been utilizing a Mapkey in my config.pro, along with the Creo Distributed Batch executable, in order to assist in a task with parts in Creo Parametric 7. However, my organization has recently upgraded to Creo Parametric 11, and using the same operation with Creo Distributed Batch, the objects ran through the task in Creo Distributed Batch now fail. Upon further research, I find this from PTC:
Is Creo Distributed Batch now longer supported with Creo 11.0 functionality and parts/assemblies? What is the new alternative to "run a mapkey defined in a config.pro" as described by Creo Distributed Batch? I've been seeing a lot of discourse about Mapkeys in Creo 11.0 and have been trying to put everything together.
I can provide more information if needed.
Mapkeys are no longer stored/loaded from config.pro files. You must first address this issue. have you migrated to the new mapkeys.pro file?
Enhancement: Separate Mapkeys Configuration
That's what I've realized, that Mapkeys within the config.pro are no longer supported for Creo 11.
Therefore, for a step like this:
Before, I would direct the "Configuration files" to my config.pro file in my Creo 7 folders. Should I now instead direct this to a new mapkeys.pro file in my Creo 11 folders? Also the title of the task is for Creo parts even if the name implies otherwise, just in case someone asks lol.
This the article explaining the new mapkey locations.
@TE_11078759 wrote:
That's what I've realized, that Mapkeys within the config.pro are no longer supported for Creo 11.
Therefore, for a step like this:
Before, I would direct the "Configuration files" to my config.pro file in my Creo 7 folders. Should I now instead direct this to a new mapkeys.pro file in my Creo 11 folders? Also the title of the task is for Creo parts even if the name implies otherwise, just in case someone asks lol.
Hi,
I suggest you to discuss the problem with PTC Support, directly.
Thank you Martin, that's my next step.
