Matching Rules retrieval is not working

Issue #1062 resolved
Javier García Manzano created an issue

I'm not sure if I'm missing some kind of configuration, but I can't seem to be able to retrieve the Standard Matching Rules.

My package.xml section looks like the following:

    <types>
        <members>Account.Standard_Account_Match_Rule_v1_0</members>
        <members>Contact.Standard_Contact_Match_Rule_v1_1</members>
        <name>MatchingRule</name>
    </types>

And this is the flow I'm following:

retrieve_panel.png

retrieve_result.png

While my metadata XML always remains empty.

retrieved_metadata.png

Cheers

Comments (7)

  1. Javier García Manzano reporter

    By the way, this same thing has been happening to us with some layouts. Eventually, we overcame the issue by manually editing the XML in order to be able to commit it to our git repository.

  2. Scott Wells repo owner

    I'll have to take a look on matching rules. As for layouts, are they packaged layouts, by chance? If so, there's a Salesforce bug around those that I need to accommodate for.

  3. Javier García Manzano reporter

    @scottwells What are packages layouts? IIRC, it was a Campaign Member layout. The related list wasn't being retrieved.

  4. Scott Wells repo owner

    Okay, thanks. By "packaged layouts" I mean layouts for objects/fields from managed packages. Turns out there's a bug in Salesforce where the metadata filename is retrieved without a necessary namespace qualification and won't save back as-is. I have an open bug to have IC automate translating to the correct name on retrieval for you.

    I'll investigate and see what I can find. I may need more info from you. I'll reach out via this issue if so.

  5. Javier García Manzano reporter

    Ok. I guess that doesn't apply to us since we don't use managed packages.

    And sure, just give me a heads up with whatever you need.

  6. Scott Wells repo owner

    Issue tracker grooming. If this is still an issue, please feel free to reopen, ideally with a concrete reproduction scenario.

  7. Log in to comment