• Industries
  • Products
  • Buy
  • Services & Support
  • Communities
  • Discussion Groups

    Autodesk Vault Customization

    Reply
    Distinguished Contributor
    FarrenYoung
    Posts: 161
    Registered: 07-13-2009
    Accepted Solution

    Added Category, color LimeGreen, errors when trying to edit in configure dialog

    70 Views, 1 Replies
    01-27-2012 04:55 PM

    I created a new category via CategoryService.AddCategory and chose LimeGreen as the color.  This appeared to work fine, I ran through some in code and set the category.  I launched Vault explorer and saw the categories were set properly, even showing my color.  However, I loaded the vault settings and went to the configure categories dialog to change category behaviors, when I started getting error messages.  I was able to see the lime green color in this dialog  When I choose edit I get a crash dialog as if Vault crashed, but Vault stays open.  When I close the error report dialog I get a Vault error saying "The given key was not present in the dictionary".  I clicked ok on it and tried again to edit and it continued to happen.  I closed Vault explorer and reloaded it and went back to the configure categories dialog.  I noticed my lime green color no longer shows up here.  If I try to copy the category I get the same dictionary error.  I can see the color on my files and I can see it in the dialog to change the category.  I deleted the category and called addCategory again this time using a color from GetAllCategoryColors() and it all worked fine, I could edit the category.

    So I am wondering if this is a known issue and if it would be possible to have it allow any color instead of one from a set of 26.

    --Farren Young (formerly AutomationGuy)
    Employee
    Posts: 414
    Registered: 12-12-2006

    Re: Added Category, color LimeGreen, errors when trying to edit in configure dia

    01-31-2012 06:45 AM in reply to: FarrenYoung

    No, I was not aware of this issue.  Thanks for letting me know.  I'll log a defect. 

    The workaround for now is to just use one of the pre-defined colors. 



    Doug Redmond
    Software Engineer
    Autodesk, Inc.
    http://justonesandzeros.typepad.com/