Skip to main content
antons87216159
Known Participant
October 29, 2020
Question

xx is either a reserved keyword or is already assigned to another item.

  • October 29, 2020
  • 1 reply
  • 485 views

I am currently working on a new project based on a previous one. It involves quite a lot of javascript and I am trying to copy an item from one document to the new one.

 

I keep getting the error message that my desired item name is already in use:

"[my object name] is either a reserved keyword or is already assigned to another item. Provide a different name for the item."

 

I know that there is no other item in my entire document with that name. Some trial and error showed that simply deleting and repasting an object would already cause the repasted item to be automatically renamed and won't allow the original name anymore.

 

Of course I could change the name, but that would mean a lot of work to change it everywhere in the code.

Is there any way to "reset" what captivate thinks is already in the project?

    This topic has been closed for replies.

    1 reply

    Paul Wilson CTDP
    Community Expert
    Community Expert
    October 31, 2020

    You could try a find and replace (CTRL+F). 

    Paul Wilson, CTDP
    antons87216159
    Known Participant
    November 3, 2020

    Hi Paul,

     

    Find and Replace doesn't find anything. It seems to only search for exisiting objects not things that are still listed in some internal list.

    I landed up having to change the code in the entire project, took a while but it works now. Still very frustrating. 😕😕

    Paul Wilson CTDP
    Community Expert
    Community Expert
    November 3, 2020

    I ran into a different but similar problem with the naming of question pools. Unlike other objects that warn you right away of a reserved keyword, in this instance, the course just wouldn't run and it was only through trial and error that I discovered it was the names or rather use of special characters in these pools that were causing the problem. It would be nice if there was a clear explanation to some of the warning messages we get. I'm glad you got it fixed. 

    Paul Wilson, CTDP