I've pulled all the metadata from a sandbox, and now as a sanity check, I'm trying to push it all back (via Force.com IDE) to the same sandbox.

It all seems to work apart from siteDotComSites metadata:

File Name:    siteDotComSites/Public_Portal1.site
Full Name:  Public_Portal1
Action:  NO ACTION
Result:  FAILED
Problem: Required field is missing: label

The package structure looks like this:


The .site file appears to be a binary. The meta.xml contains:

<?xml version="1.0" encoding="UTF-8"?>
<SiteDotCom xmlns="http://soap.sforce.com/2006/04/metadata">

I haven't done any work on the sites part so don't know any details about what's supposed to be working. However the error message seems incorrect. I can see a label in the XML.

Is this unsupported metadata as described here?:


If so why can I retrieve it? Should I just remove it from the package manifest?

  • Did you find solution for that problem? Am facing the same issue now. Dec 20 '16 at 19:32
  • @salesforce-dev No. From what I recall it's not deployable.
    – powlo
    Dec 21 '16 at 11:46
  • In my case I was trying to deploy a VF Page w/out the meta.xml file. Problem solved.
    – MDMoore313
    Aug 21 '17 at 18:56

Looks like it is a general migration tool limitation. Whenever you are trying to deploy a component (this case was a SiteDotComSites for us too) without its meta.xml, it will run into a deployment issue. It is especially annoying when you are using git or other version control system and trying to deploy the delta only. Therefore even if your metadata xml hasn't changed with your deployable component, you still have to include a dummy change in the meta file to work this migration tool limitation around.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.