Author Topic: UNABLE TO EXECUTE COMMAND - COMMAND NOT AVAILABLE  (Read 1307 times)

dryfly52

  • Newbie
  • *
  • Posts: 5
UNABLE TO EXECUTE COMMAND - COMMAND NOT AVAILABLE
« on: May 16, 2020, 11:29:48 AM »
Hi,

When importing commands from another profile I get UNABLE TO EXECUTE COMMAND - COMMAND NOT AVAILABLE inplace of one of the steps within a command. The command that it is refering to is available within the profile?

Does any one no what is causing this.


Many thanks

Pfeil

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 4782
  • RTFM
Re: UNABLE TO EXECUTE COMMAND - COMMAND NOT AVAILABLE
« Reply #1 on: May 16, 2020, 11:38:11 AM »
Command references for the "Execute Another Command" action's "Execute selected command" option are only maintained if the referenced command is imported as part of the same profile as the referencing command.

E.G. if you have "Command A" referencing "Command B" using the "Execute selected command" option, both "Command A" and "Command B" need to be part of the same profile, exported together to the same .vap, and imported together, in order for the reference to remain valid.

dryfly52

  • Newbie
  • *
  • Posts: 5
Re: UNABLE TO EXECUTE COMMAND - COMMAND NOT AVAILABLE
« Reply #2 on: May 16, 2020, 01:12:20 PM »
Hi,

So any command with dependancies needs to be treated as one in terms of importing/exporting ie they all need to be selected.

This is true even though the top level command is the only one that has been edited and the lower command already exists unedited in the importing profile?


Many thanks


Pfeil

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 4782
  • RTFM
Re: UNABLE TO EXECUTE COMMAND - COMMAND NOT AVAILABLE
« Reply #3 on: May 16, 2020, 01:19:04 PM »
The internal ID for a command is not conserved when exporting/importing, so it doesn't matter whether a command comes from the same profile or not if you don't export them into the same file.

Commands that reference using the "Execute selected command" option each other must be exported and imported together.

Commands that reference other commands using the "Execute by name (Advanced)" option look up the target command by its command phrase, meaning the internal ID is irrelevant, however that options comes with possible caveats, as noted in the "'Execute Another Command'" section of VoiceAttackHelp.pdf

dryfly52

  • Newbie
  • *
  • Posts: 5
Re: UNABLE TO EXECUTE COMMAND - COMMAND NOT AVAILABLE
« Reply #4 on: May 18, 2020, 06:33:50 AM »
HI,


Something to get my head round   ;)

Thanks for your help

Regards

Chris