+ Start a Discussion
EndaEnda 

Ant Deploy problem with Knowledge Article Page Layouts - Cannot specify: detailHeading for Layout of a Knowledge Article Type

Hey,

Has anyone seen the following error when trying to deploy a Knowledge Article page layout:

Cannot specify: detailHeading for Layout of a Knowledge Article Type

My page layout looks like this:
 
<?xml version="1.0" encoding="UTF-8"?>
<Layout xmlns="http://soap.sforce.com/2006/04/metadata">
    <layoutSections>
        <customLabel>false</customLabel>
        <detailHeading>false</detailHeading>
        <editHeading>false</editHeading>
        <label>Information</label>
        <layoutColumns>
            <layoutItems>
                <field>Publish_to_Website__c</field>
            </layoutItems>
            <layoutItems>
                <field>Attach_Article_to_S3__c</field>
            </layoutItems>
            <layoutItems>
                <field>S3_Article_Link__c</field>
            </layoutItems>
            <layoutItems>
                <field>Information__c</field>
            </layoutItems>
        </layoutColumns>
        <style>OneColumn</style>
    </layoutSections>
</Layout>


I've tried removing the detailHeading tag altogether as well as changing the value between true and false but to no avail. 
I also tried with a package.xml version of 29.0, 30.0 and 31.0 and they all had the same behaviour.
Any suggestions would be hugely appreciated.


Cheers,
Enda.
ShashankShashank (Salesforce Developers) 
Salesforce R&D are made aware of this issue and they are working on it. As of now, there is no ETA yet. This has been identified for layouts with formula fields included. You can probably try removing the formula fields. Another workaround would be to manually deploy article type layouts which have formula fields until this is fixed.
Marcel dos SantosMarcel dos Santos
I'm trying to deploy a change set with a Knowledge Base article type layout and I'm getting that same error.

Did you ever find a solution for this problem?
EndaEnda
Hey Marcel - no I never got a resolution to this error and ended up having to deploy those layouts manually.