function readOnly(count){ }
Sign Up ›
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
Learn More

Browse by Topic
ShowAll Questionssorted byDate Posted
+ Start a Discussion
deux4everdeux4ever 

Error when deploying custom object with IDE

I am trying to deploy a custom object I created in my sandbox and getting a failure. I had orginally tried to use change sets on just the custom object, but read that using IDE will solve my issue (I was getting a "Cannot set ControlledByParent on a CustomObject without a MasterDetail relationship field" failure message). So installed Eclipse and added Force.com and when I try to deploy just my custom object, I get a failure message. The odd part is that the actual custom object metadata is being deployed fine, but it looks like it is also trying to send test classes that I do not want to send over. Is there anyway I can just send the custom object and nothing else? When deploying the custom object, I drilled down to the objects folder and sent it from there. Below is the log of the failure. 
*** Deployment Log ***
Result: FAILED
Date: June 6, 2014 9:49:05 AM PDT

# Deployed From:
   Project name: Sandbox
   Username: joseph.yu@emeraldnw.com.sandbox
   Endpoint: test.salesforce.com

# Deployed To:
   Username: joseph.yu@emeraldnw.com
   Endpoint: www.salesforce.com

# Deploy Results:
   File Name:    objects/Price_Exception__c.object
   Full Name:  Price_Exception__c.Current_Product__c
   Action:  UPDATED
   Result:  SUCCESS
   Problem: n/a

   File Name:    objects/Price_Exception__c.object
   Full Name:  Price_Exception__c.Account_Name__c
   Action:  UPDATED
   Result:  SUCCESS
   Problem: n/a

   File Name:    objects/Price_Exception__c.object
   Full Name:  Price_Exception__c.Approval_Date__c
   Action:  UPDATED
   Result:  SUCCESS
   Problem: n/a

   File Name:    objects/Price_Exception__c.object
   Full Name:  Price_Exception__c.Approval_Status__c
   Action:  UPDATED
   Result:  SUCCESS
   Problem: n/a

   File Name:    objects/Price_Exception__c.object
   Full Name:  Price_Exception__c.Collected_Oil_Gallons_YTD__c
   Action:  UPDATED
   Result:  SUCCESS
   Problem: n/a

   File Name:    objects/Price_Exception__c.object
   Full Name:  Price_Exception__c.Current_Oil_Rate__c
   Action:  UPDATED
   Result:  SUCCESS
   Problem: n/a

   File Name:    objects/Price_Exception__c.object
   Full Name:  Price_Exception__c.Current_Price_Ranking__c
   Action:  UPDATED
   Result:  SUCCESS
   Problem: n/a

   File Name:    objects/Price_Exception__c.object
   Full Name:  Price_Exception__c.Effective_Date__c
   Action:  UPDATED
   Result:  SUCCESS
   Problem: n/a

   File Name:    objects/Price_Exception__c.object
   Full Name:  Price_Exception__c.Notes__c
   Action:  UPDATED
   Result:  SUCCESS
   Problem: n/a

   File Name:    objects/Price_Exception__c.object
   Full Name:  Price_Exception__c.Price_Exception_Reason__c
   Action:  UPDATED
   Result:  SUCCESS
   Problem: n/a

   File Name:    objects/Price_Exception__c.object
   Full Name:  Price_Exception__c.Proposed_Oil_Rate__c
   Action:  UPDATED
   Result:  SUCCESS
   Problem: n/a

   File Name:    objects/Price_Exception__c.object
   Full Name:  Price_Exception__c.Proposed_Price_Ranking__c
   Action:  UPDATED
   Result:  SUCCESS
   Problem: n/a

   File Name:    objects/Price_Exception__c.object
   Full Name:  Price_Exception__c.Rec_Unique__c
   Action:  UPDATED
   Result:  SUCCESS
   Problem: n/a

   File Name:    objects/Price_Exception__c.object
   Full Name:  Price_Exception__c.Recalled_Date__c
   Action:  UPDATED
   Result:  SUCCESS
   Problem: n/a

   File Name:    objects/Price_Exception__c.object
   Full Name:  Price_Exception__c.Rejected_Date__c
   Action:  UPDATED
   Result:  SUCCESS
   Problem: n/a

   File Name:    objects/Price_Exception__c.object
   Full Name:  Price_Exception__c.Rolling_12_Month_Oil_YTD__c
   Action:  UPDATED
   Result:  SUCCESS
   Problem: n/a

   File Name:    objects/Price_Exception__c.object
   Full Name:  Price_Exception__c.Shipping_City__c
   Action:  UPDATED
   Result:  SUCCESS
   Problem: n/a

   File Name:    objects/Price_Exception__c.object
   Full Name:  Price_Exception__c.Shipping_State__c
   Action:  UPDATED
   Result:  SUCCESS
   Problem: n/a

   File Name:    objects/Price_Exception__c.object
   Full Name:  Price_Exception__c.Shipping_Street__c
   Action:  UPDATED
   Result:  SUCCESS
   Problem: n/a

   File Name:    objects/Price_Exception__c.object
   Full Name:  Price_Exception__c.Shipping_Zip_Code__c
   Action:  UPDATED
   Result:  SUCCESS
   Problem: n/a

   File Name:    objects/Price_Exception__c.object
   Full Name:  Price_Exception__c
   Action:  UPDATED
   Result:  SUCCESS
   Problem: n/a

   File Name:    objects/Price_Exception__c.object
   Full Name:  Price_Exception__c.Oil
   Action:  UPDATED
   Result:  SUCCESS
   Problem: n/a

   File Name:    objects/Price_Exception__c.object
   Full Name:  Price_Exception__c.All
   Action:  UPDATED
   Result:  SUCCESS
   Problem: n/a

   File Name:    objects/Price_Exception__c.object
   Full Name:  Price_Exception__c.Approved
   Action:  UPDATED
   Result:  SUCCESS
   Problem: n/a

   File Name:    objects/Price_Exception__c.object
   Full Name:  Price_Exception__c.Pending
   Action:  UPDATED
   Result:  SUCCESS
   Problem: n/a

   File Name:    package.xml
   Full Name:  package.xml
   Action:  UPDATED
   Result:  SUCCESS
   Problem: n/a

# Test Results:

Run Failures:
  ConvertLead.basicTestWithoutConvertedStatus System.DmlException: Insert failed. First exception on row 0; first error: FIELD_CUSTOM_VALIDATION_EXCEPTION, CITY AND STATE ARE REQUIRED FOR THIS ENTRY: []
  ConvertLead.basicTestwith System.DmlException: Insert failed. First exception on row 0; first error: FIELD_CUSTOM_VALIDATION_EXCEPTION, CITY AND STATE ARE REQUIRED FOR THIS ENTRY: []
  ConvertLead.basicTestwithAccount System.DmlException: Insert failed. First exception on row 0; first error: FIELD_CUSTOM_VALIDATION_EXCEPTION, CITY AND STATE ARE REQUIRED FOR THIS ENTRY: []
  ConvertLead.basicTestwithAccounts System.DmlException: Insert failed. First exception on row 0; first error: FIELD_CUSTOM_VALIDATION_EXCEPTION, CITY AND STATE ARE REQUIRED FOR THIS ENTRY: []
  createAndAttachPDF.basicTest System.DmlException: Insert failed. First exception on row 0; first error: FIELD_CUSTOM_VALIDATION_EXCEPTION, CITY AND STATE ARE REQUIRED FOR THIS ENTRY: []
  submitForApproval.basicTest System.DmlException: Insert failed. First exception on row 0; first error: FIELD_CUSTOM_VALIDATION_EXCEPTION, CITY AND STATE ARE REQUIRED FOR THIS ENTRY: []
  testSendEmailFlowPlugin.attachmentTest System.DmlException: Insert failed. First exception on row 0; first error: FIELD_CUSTOM_VALIDATION_EXCEPTION, CITY AND STATE ARE REQUIRED FOR THIS ENTRY: []
  testSendEmailFlowPlugin.basicTest System.DmlException: Insert failed. First exception on row 0; first error: FIELD_CUSTOM_VALIDATION_EXCEPTION, CITY AND STATE ARE REQUIRED FOR THIS ENTRY: []
  testSendEmailFlowPlugin.basicTestwithCCEmail System.DmlException: Insert failed. First exception on row 0; first error: FIELD_CUSTOM_VALIDATION_EXCEPTION, CITY AND STATE ARE REQUIRED FOR THIS ENTRY: []
  testSendEmailFlowPlugin.basicTestwithTextAttachment System.DmlException: Insert failed. First exception on row 0; first error: FIELD_CUSTOM_VALIDATION_EXCEPTION, CITY AND STATE ARE REQUIRED FOR THIS ENTRY: []
  testSendEmailFlowPlugin.basicTestwithTextAttachmentandCCEmail System.DmlException: Insert failed. First exception on row 0; first error: FIELD_CUSTOM_VALIDATION_EXCEPTION, CITY AND STATE ARE REQUIRED FOR THIS ENTRY: []
  testSendEmailFlowPlugin.basicTestwithpdfAttachment System.DmlException: Insert failed. First exception on row 0; first error: FIELD_CUSTOM_VALIDATION_EXCEPTION, CITY AND STATE ARE REQUIRED FOR THIS ENTRY: []

Edwin VijayEdwin Vijay
Maybe, you could try splitting up your changeset into two. If you still get the same error,  try removing the part causing the error and then deploy. You could later manually configure in production.

However, i would suggest you fix your test classes.
deux4everdeux4ever
That's the odd part, I don't want the test cases to even get sent. I just want to deploy the custom object, nothing else. How can I just deploy that? I tried it both with IDE and changesets to no avail.
Edwin VijayEdwin Vijay
Then changesets would be the best bet i believe. Try breaking up your changeset into chunks and deploy?