Forum Discussion

Dara_s's avatar
Dara_s
Ideator I
7 years ago

Add newly created ItemType in custom Category(TOC Access)

Hello,

   I have imported a package with a custom solution which has an ItemType "New ItemType" in a Category1. But in this package I haven`t added the List "Categories" so when I imported it, there was no value "Category1", which is normal. Anyways somehow the category exists(only in the TOC not in the List of categories).

My question is how could I add to this category "Category1" a new ItemType "ItemType2" that I want to create? When I didn`t export the list "Categories" and so in it, it doesn`t exist the value "Category1". Should I create again this Category1 in the list "Categories" in order to add this new "ItemType2" to Category1?

I would appreciate any help! Thank you!

Regards,

Dara

7 Replies

  • Hi Dara,

    The behavior you're seeing is interesting! I believe that since the "TOC Access" item exists as part of your exported ItemType, when the TOC is built, that "TOC Access" item is found and populated. 

    To answer your question, adding "category1" to your "Categories" list is your best bet. Without adding that item to the list, you won't be able to assign item2 to your new category, since you'll be unable to select it when assigning TOC Acess to ItemType2.

    AJ

    • Dara_s's avatar
      Dara_s
      Ideator I

      Ni AJ Sebastian,

      Thank you for the quick reply, appreciate it! If I do so, could I be able to export and import properly? Because I already tried this and when I import I get the following error:

      ****ErrorMessage****

      Import package ARAS.Solution.Simulation failed with message:

      <SOAP-ENV:Envelope xmlns:SOAP-ENV="">schemas.xmlsoap.org/.../"><SOAP-ENV:Body><SOAP-ENV:Fault xmlns:af="">www.aras.com/.../faultcode><faultstring><![CDATA[ITPresentationConfiguration already exists.]]></faultstring><detail><af:legacy_detail><![CDATA[ITPresentationConfiguration already exists.]]></af:legacy_detail><af:legacy_faultstring><![CDATA[Violation of PRIMARY KEY constraint.]]></af:legacy_faultstring></detail></SOAP-ENV:Fault></SOAP-ENV:Body></SOAP-ENV:Envelope>
      Updating package to failed release status
              ********************

      Thank you again!

      Dara

      • asebastian's avatar
        asebastian
        New Member

        Does this happen only when you add the updated "categories" list to your package?