EmailTemplates aren't available for retrieval

Issue #109 resolved
Petr Švestka created an issue

EmailTemplate items not offered to be selected and retrieved.

Assuming there'll be more item types that aren't available as of yet. Is there a list of what's (not) available?

Thanks.

Comments (8)

  1. Scott Wells repo owner

    Petr, nothing is explicitly omitted from the list of metadata types. I'm just using the SOAP metadata API (describeMetadata() and listMetadata()) to get the available metadata types and presenting those.

    Having said that, there have been a few bugs in this area where I was accidentally filtering out items in the resulting tree, so it's possible there are still instances of such bugs. Let me take a look and see if I can figure out what's going on with this one (and likely other ones that might be subject to the same issue).

  2. Scott Wells repo owner

    Yep, looks like for some reason EmailTemplate doesn't behave like the other metadata types that are designated as foldered metadata types (e.g., Report, Dashboard, and Document). There's no corresponding EmailTemplateFolder metadata type for enumerating folder contents. You can probably see the corresponding logged warning in idea.log ("Failed to query the metadata for folder type EmailTemplate"). I'll have to dig in and see if I can figure out why this one is behaving differently and what to do about it.

  3. Scott Wells repo owner

    Looks like an inconsistency in Salesforce. The folder metadata type of EmailTemplate is EmailFolder, not EmailTemplateFolder. Should be an easy enough fix now that I know the problem.

  4. Scott Wells repo owner

    Okay, I have a fix for this that will be in the next plugin update. I'll try to push that out later today or tonight.

  5. Scott Wells repo owner

    Should be resolved int he latest build. Let me know if it isn't.

    Oh, and I did notice one thing worth mentioning...if you pull down foldered metadata in the unfiled$public folder, the metadata retrieval API doesn't include a *-meta.xml for that directory so you can't deploy its contents. And manual creation of that metadata file doesn't resolve the issue either. Explicit folders work fine, though. I'll research this a bit more as I'm not sure what is and isn't supported for that special folder.

  6. Log in to comment