Not in package.xml error
549 views
Skip to first unread message
Robert Conner
Jul 18, 2016, 3:56:04 PM7/18/16
to Illuminated Cloud General Discussion
Did a force save .. Deployment Complete: Deployed 0/1 components to QA2 in 11s 350ms with status FAILED.
The Event Log didn't report any errors. When I login to Salesforce to see, I got to the Deployment Status section and see:
Payment_Settings__c.Fail_Days__c Custom Field 0 0 Not in package.xml
I'm not entirely sure how to solve this. How can I add it to my package.xml. Is it the local package.xml or is there one in SF that I need to edit somehow?
I actually don't even have a local package.xml. Can I regenerate it somehow?
The Event Log didn't report any errors. When I login to Salesforce to see, I got to the Deployment Status section and see:
Payment_Settings__c.Fail_Days__c Custom Field 0 0 Not in package.xml
I'm not entirely sure how to solve this. How can I add it to my package.xml. Is it the local package.xml or is there one in SF that I need to edit somehow?
I actually don't even have a local package.xml. Can I regenerate it somehow?
Scott
Jul 18, 2016, 4:09:29 PM7/18/16
to Illuminated Cloud General Discussion
Robert, Illuminated Cloud generates a package.xml when deploying through the metadata API. Let's gather some additional info on exactly what it's trying to deploy. Go into Help>Debug Log Settings and add the following entries:
#com.illuminatedcloud.intellij.builder.ForceComBuilder
#com.illuminatedcloud.intellij.builder.ForceComMetadataApiDeployer
Rerun the force save and send me the resulting info in idea.log (Help>Show Log in Explorer/Finder). Feel free to send it via email if it contains sensitive info.
Regards,
Scott
Robert Conner
Jul 18, 2016, 4:12:17 PM7/18/16
to Illuminated Cloud General Discussion
Just to add to that last comment, I was deploying the Custom Setting metadata of Payment_Setting__c.object
Scott
Jul 18, 2016, 4:22:45 PM7/18/16
to Illuminated Cloud General Discussion
Robert, I can reproduce this if I set up my metadata subscription such that the custom setting is not selected under CustomObject and only some of its fields are selected under CustomField. If I either select all of the fields for that custom setting under CustomField or select the custom setting itself under CustomObject, it deploys just fine. Can you check this on your end and see if it's a partial selection of the custom setting?
Robert Conner
Jul 18, 2016, 4:41:03 PM7/18/16
to Illuminated Cloud General Discussion
It's a brand new Object. So it does not appear as a checkbox that I
can check under the metadata subscription. I exported it out of a
different sandbox. Pushed it to git on another computer. Pulled into my
filesystem and tried to push it to a different sandbox.
Reply all
Reply to author
Forward
0 new messages