function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
Sachin10Sachin10 

Custom console component contains an invalid location.

Hi Team,
We are getting the following error while deploying
Custom console component contains an invalid location.

Any pointers/suggestions are welcome

Many Thanks :)
Ashish_SFDCAshish_SFDC
Hi Sachin,


See the below link,

https://developer.salesforce.com/forums/ForumsMain?id=906F00000009FQgIAM


Regards,
Ashish
Sachin10Sachin10
@Ashish,
Thanks for your reply.
The issue was resolved by myself.
Is is due to differenece in the Caps for the Location Value
The_London_ScottThe_London_Scott
I get the same error and believe it has to do with the mismatch between Spring '14 (in our sandbox) and Winter '14 (in production; we haven't been updated yet). In Spring '14, additional display styles options are available for custom console components, and you can specify height or width in % as well as in pixels. My deployment errors come on page layouts where I have custom console components. I previously defined some of the dimensions in % and experimented with other styles, for prior to my deployment attempt I set all dimensions to be pixels and style to be 'stack' in an effort to be compatible with Winter '14. However this does not seem to have worked.

I find no guidance in SFDC Known Issues about how to deploy changes to page layouts containing custom console components when the source sandbox is in Spring and target organization is in winter.
The_London_ScottThe_London_Scott
Examining the XML differences between the relevant part of a page layout in production and the test version I want to replace it with, I find that the <location> tags have values in lower-case in production (Winter '14) and capitalized in test (Spring '14). I believe this may be the source of failure. My attempt to push this change was made using change sets, so the third-party issue does not come into it.

Production:

<customConsoleComponents>
        <primaryTabComponents>
            <component>
                <height>250</height>
                <location>bottom</location>
                <visualforcePage>AccountCEIsAssets</visualforcePage>
            </component>
            <component>
                <location>right</location>
                <visualforcePage>AccountRelatedLists</visualforcePage>
                <width>600</width>
            </component>
        </primaryTabComponents>
    </customConsoleComponents>


Test:

    <customConsoleComponents>
        <subtabComponents>
             <component>
                <height>125</height>
                <location>Bottom</location>
                <visualforcePage>AccountCEIsAssets</visualforcePage>
            </component>
          <component>
                <location>Right</location>
                <visualforcePage>AccountRelatedLists</visualforcePage>
                <width>650</width>
            </component>
        </subtabComponents>
    </customConsoleComponents>