Unable to retrieve Territory2Model xml file with IlluminatedCloud

Issue #1410 resolved
Thomas Creemers created an issue

Dear,

I’m unable to retrieve my Territory2Model xml file with Illuminated Cloud. It shows up in the Project Structure but it doesn’t show up in the Retrieve screen.

The only thing retrieved is

  • all the territory2 files
  • the territory2Type

The Territory2Model file is not retrieved.

Version: 1.8.5.3
Tested with API 43.0 & 46.0

Comments (9)

  1. Scott Wells repo owner

    Hi, Thomas. When you say that it shows up in the project structure, do you mean the local files themselves are visible in the left-hand project view or something else? Have you added these metadata objects to your metadata subscription? That may well be the issue. Do you see them in the Retrieve screen when you uncheck Subscribed Only?

    Let's start there and see if that provides some insight into the issue. Thanks!

  2. Scott Wells repo owner

    Thanks. That helps. And so when you retrieve using those Custom selections, what happens? We can also get details by having you enable debug logging for metadata retrieval, reproducing the issue, and providing the resulting idea.log using Help>Show Log in Explorer/Finder/Files. Feel free to attach or email that log file if you'd like.

  3. Thomas Creemers reporter

    Hereby some pictures of the issue:

    • The last picture is what I retrieve in my directory.

      • Here you see that it only contains the subfolder ‘territories’. This one is filled with as expected *.territory2 files
      • In the folder Etex_One_CRM_Territory_Model you however have a missing xml file called ‘Etex_One_CRM_Territory_Model.territory2Model’ (In my Case as it is org specific)

    Hereby a Screenshot of what I retrieve with the normal Migration Toolkit from SF (Ant Script)

  4. Thomas Creemers reporter

    SF also subscripes that the package.xml should be parsed like the below.
    (source: https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_territory2.htm?search_text=Territory)

        <types>
            <members>FY13</members>
             <name>Territory2Model</name>
        </types>    
        <types>
            <members>FY13.USA</members>
            <members>FY13.Worldwide_Sales</members>
            <name>Territory2</name>
        </types>
        <types>
            <members>Default</members>
            <name>Territory2Type</name>
        </types>
    

    Illuminated Cloud for me parses (while using the 'Add to Metadata Subscription…' ) currently as below, potentially related to the issue.

        <types>
            <members>Etex_One_CRM_Territory_Model</members>
            <members>Etex_One_CRM_Territory_Model/territories</members>
            <members>Etex_One_CRM_Territory_Model/territories/EBP</members>
            <members>Etex_One_CRM_Territory_Model/territories/EBP_AR</members>
            <members>Etex_One_CRM_Territory_Model/territories/EBP_AR_01</members>
            <members>Etex_One_CRM_Territory_Model/territories/EBP_AR_02</members>
            <name>Territory2</name>
        </types>
        <types>
            <members>Etex_Default</members>
            <name>Territory2Type</name>
        </types>
    
  5. Scott Wells repo owner

    Yes, that looks like it's the root cause. IC isn't properly processing this metadata type. There's another quite non-standard metadata type similar to this for Wave metadata. I'll look at including this in the build after the one I'm working on now (which is also a huge set of metadata deployment/retrieval/subscription enhancements) to make IC more aware of this special metadata type. Thanks for providing the info.

  6. Scott Wells repo owner

    I've just submitted a fix for this for inclusion in the next build. I'm currently targeting Thursday or Friday of this week to release it.

  7. Log in to comment