Issue deploying email templates folders/document folders

Issue #194 resolved
Nathen Drees created an issue

I'm not sure if this is something I'm doing, or if there's an issue with the package zip that IC is creating, but i'm having issues deploying code that contains email templates and documents in folders.

To reproduce: create an email template folder with at least 1 email template, and a meta file for both. Then try to deploy the metadata through IC and you should get the error:

Error:(1, 1) An object 'Foo' of type Email Template was named in package.xml, but was not found in zipped directory.

The meta file for the folder looks something like:

<?xml version="1.0" encoding="UTF-8"?>
<DocumentFolder xmlns="http://soap.sforce.com/2006/04/metadata">
    <accessType>Public</accessType>
    <name>Foo</name>
    <publicFolderAccess>ReadWrite</publicFolderAccess>
</DocumentFolder>

I'm also receiving the error Error:(1, 1) An object 'unfiled$public' of type EmailTemplate was named in package.xml, but was not found in zipped directory, but there is no meta file for this folder (unfiled$public is not deployable I believe, but should already exist). Not there is no entry for just unfiled$public in the package.xml.

Here's the email template portion of the package.xml:

<?xml version="1.0" encoding="UTF-8"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
    <types>
        <members>Foo</members>
        <members>Foo/FooExample</members>
        <members>unfiled$public/ContactFollowUpSAMPLE</members>
        <members>unfiled$public/LeadsNewassignmentnotificationSAMPLE</members>
        <members>unfiled$public/LeadsWebtoLeademailresponseSAMPLE</members>
        <members>unfiled$public/SUPPORTCaseResponsewithSolutionSAMPLE</members>
        <members>unfiled$public/SUPPORTCaseescalationnotificationSAMPLE</members>
        <members>unfiled$public/SUPPORTNewassignmentnotificationSAMPLE</members>
        <members>unfiled$public/SUPPORTSelfServiceNewCommentNotificationSAMPLE</members>
        <members>unfiled$public/SUPPORTSelfServiceNewUserLoginInformationSAMPLE</members>
        <members>unfiled$public/SUPPORTSelfServiceResetPasswordSAMPLE</members>
        <members>unfiled$public/SUPPORTWebtoCaseemailresponseSAMPLE</members>
        <name>EmailTemplate</name>
    </types>
    <version>35.0</version>
</Package>

Comments (6)

  1. Scott Wells repo owner

    Nathan, this looks like a bug with foldered metadata types. I'll need to reproduce it on my end and it should be pretty easy to fix once I've done so.

  2. Scott Wells repo owner

    Nathan, I did find an issue with deployment of foldered metadata types that was introduced very recently. I already have a fix and will be posting an update tonight or tomorrow morning.

  3. Nathen Drees reporter

    Thanks Scott,

    We have a temporary work around using ant and the migration tool, but this will be nice.

    Sort of related, but could we get the ability to define deployment configurations with more options? The migration tool has a lot of switches around log levels, what unit tests to run (if any), etc. would be nice to be able to set this via the UI as a run configuration, or have the IDE spit out an ant file that can use the creds already in the project. Then we can reuse intellijs built in ant runner.

  4. Scott Wells repo owner

    Nathen (sorry for the previous misspelling!), I'll be uploading the fix for this very shortly. Look for the 1.6.7.4 update. As for the request for more configuration options on deployment and/or something that creates an ant target for you, please open a new enhancement request detailing the use case if you don't mind. In particular, I'd like to understand which options you'd like to see included (there are many for the metadata deployment API) and for ones like running tests, what the expected behavior might be vs. the current integrated test runner. Thanks!

  5. Log in to comment