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
zeezackisbackzeezackisback 

Cloning Orgs using Force.com

I have been trying to duplicate an org from some test accounts.

 

I've made some records and a custom field etc... in the first org. The second org is blank.

 

 

I've connected to the 1st org using Force.com eclipse... pulled in ALL required apex,classes,objects... ticked the whole lot.

 

then I tried deploying to the second org... I've had to change a few things like user of the org to this user.... but there are other errors which are stopping deployment...

 

in particular reports...

 

Please can anyone help me clone the data structure, schema and data from one ORG to another?

 

 

 

*** Deployment Log ***
Result: FAILED
Date: 29 May 2009 14:07:43 BST

# Deployed From:
   Project name: Test org1
   Username: *****@XXX.com
   Endpoint: www.salesforce.com

# Deployed To:
   Username: ****@hotmail.com
   Endpoint: www.salesforce.com

# Deploy Results:
   File Name:    reports/TEST1-meta.xml
   Full Name:  TEST1
   Action:  NO ACTION
   Result:  FAILED
   Problem: Not in package.xml

   File Name:    reports/TEST1/TEST1.report
   Full Name:  TEST1/TEST1
   Action:  NO ACTION
   Result:  FAILED
   Problem: Cannot find folder:TEST1

   File Name:    workflows/Account.workflow
   Full Name:  Account.TEST1
   Action:  NO ACTION
   Result:  FAILED
   Problem: In field: recipient - no User named rob.lone@pixpaycard.com found

   File Name:    layouts/Account-Account %28Marketing%29 Layout.layout
   Full Name:  Account-Account %28Marketing%29 Layout
   Action:  UPDATED
   Result:  SUCCESS
   Problem: n/a

   File Name:    layouts/Account-Account %28Sales%29 Layout.layout
   Full Name:  Account-Account %28Sales%29 Layout
   Action:  UPDATED
   Result:  SUCCESS
   Problem: n/a

   File Name:    layouts/Account-Account %28Support%29 Layout.layout
   Full Name:  Account-Account %28Support%29 Layout
   Action:  UPDATED
   Result:  SUCCESS
   Problem: n/a

   File Name:    layouts/Account-Account Layout.layout
   Full Name:  Account-Account Layout
   Action:  UPDATED
   Result:  SUCCESS
   Problem: n/a

   File Name:    layouts/TEST1__c-TEST1 Layout.layout
   Full Name:  TEST1__c-TEST1 Layout
   Action:  NO ACTION
   Result:  SUCCESS
   Problem: n/a

   File Name:    objectTranslations/TEST1__c-en_US.objectTranslation
   Full Name:  TEST1__c-en_US
   Action:  NO ACTION
   Result:  SUCCESS
   Problem: n/a

   File Name:    objects/Account.object
   Full Name:  Account.Active__c
   Action:  NO ACTION
   Result:  SUCCESS
   Problem: n/a

   File Name:    objects/Account.object
   Full Name:  Account.CustomerPriority__c
   Action:  NO ACTION
   Result:  SUCCESS
   Problem: n/a

   File Name:    objects/Account.object
   Full Name:  Account.NumberofLocations__c
   Action:  NO ACTION
   Result:  SUCCESS
   Problem: n/a

   File Name:    objects/Account.object
   Full Name:  Account.SLAExpirationDate__c
   Action:  NO ACTION
   Result:  SUCCESS
   Problem: n/a

   File Name:    objects/Account.object
   Full Name:  Account.SLASerialNumber__c
   Action:  NO ACTION
   Result:  SUCCESS
   Problem: n/a

   File Name:    objects/Account.object
   Full Name:  Account.SLA__c
   Action:  NO ACTION
   Result:  SUCCESS
   Problem: n/a

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

   File Name:    objects/Account.object
   Full Name:  Account.UpsellOpportunity__c
   Action:  NO ACTION
   Result:  SUCCESS
   Problem: n/a

   File Name:    objects/Account.object
   Full Name:  Account
   Action:  NO ACTION
   Result:  SUCCESS
   Problem: n/a

   File Name:    objects/Account.object
   Full Name:  Account.Billing
   Action:  NO ACTION
   Result:  SUCCESS
   Problem: n/a

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

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

   File Name:    profiles/Admin.profile
   Full Name:  Admin
   Action:  UPDATED
   Result:  SUCCESS
   Problem: n/a

   File Name:    profiles/ContractManager.profile
   Full Name:  ContractManager
   Action:  UPDATED
   Result:  SUCCESS
   Problem: n/a

   File Name:    profiles/Custom%3A Marketing Profile.profile
   Full Name:  Custom%3A Marketing Profile
   Action:  UPDATED
   Result:  SUCCESS
   Problem: n/a

   File Name:    profiles/Custom%3A Sales Profile.profile
   Full Name:  Custom%3A Sales Profile
   Action:  UPDATED
   Result:  SUCCESS
   Problem: n/a

   File Name:    profiles/Custom%3A Support Profile.profile
   Full Name:  Custom%3A Support Profile
   Action:  UPDATED
   Result:  SUCCESS
   Problem: n/a

   File Name:    profiles/CustomerManager.profile
   Full Name:  CustomerManager
   Action:  UPDATED
   Result:  SUCCESS
   Problem: n/a

   File Name:    profiles/MarketingProfile.profile
   Full Name:  MarketingProfile
   Action:  UPDATED
   Result:  SUCCESS
   Problem: n/a

   File Name:    profiles/Partner.profile
   Full Name:  Partner
   Action:  UPDATED
   Result:  SUCCESS
   Problem: n/a

   File Name:    profiles/ReadOnly.profile
   Full Name:  ReadOnly
   Action:  UPDATED
   Result:  SUCCESS
   Problem: n/a

   File Name:    profiles/SolutionManager.profile
   Full Name:  SolutionManager
   Action:  UPDATED
   Result:  SUCCESS
   Problem: n/a

   File Name:    profiles/Standard.profile
   Full Name:  Standard
   Action:  UPDATED
   Result:  SUCCESS
   Problem: n/a

   File Name:    profiles/StandardAul.profile
   Full Name:  StandardAul
   Action:  UPDATED
   Result:  SUCCESS
   Problem: n/a

   File Name:    workflows/Account.workflow
   Full Name:  Account
   Action:  NO ACTION
   Result:  SUCCESS
   Problem: n/a

   File Name:    workflows/Account.workflow
   Full Name:  Account.TEST1
   Action:  NO ACTION
   Result:  SUCCESS
   Problem: n/a

   File Name:    workflows/TEST1__c.workflow
   Full Name:  TEST1__c
   Action:  NO ACTION
   Result:  SUCCESS
   Problem: n/a

# Test Results:
   n/a

 

 

 

Best Answer chosen by Admin (Salesforce Developers) 
MycodexMycodex

I know this post is old but better late than never since I regularly see unfinished threads on this forum.

 

I ran into a similar issue. My output was identical. I've deployed using Eclipse countless times but I just updated Eclipse. The issue was that I was trying to deploy using the Navigator view. Switching over to the Package Explorer view solved my issue.

 

The Package Explorer view can be enabled by clicking

Window | Show View | Package Explorer

 

Both views are needed when using Eclipse. Package Explorer will deploy changes while Navigator should only be used to delete files off the local machine. I believe if you try to delete a file through Package Explorer that you are effectively deleting them off the server as well.

All Answers

zeezackisbackzeezackisback

*its reporting TEST1 is not in package.xml - even though it is?

* its reporting it can not find TEST1 in reports.. even though it exists. - I just need to change rob.lone@pixpaycard.com to my hotmail account - that I used to register for the second org

zeezackisbackzeezackisback

...Is there any method known to man that can do this

 

is there a way of doing it via  telnet?

how to deploy org 1 to org2, using Force.com?

 

Robs

 

 

zeezackisbackzeezackisback

Is there an api,

that will allow me to EXPORT the custom objects and then import them into a new org?

BulentBulent

make sure you are using the correct version of the eclipse plugin and it's properly setup.

you are basically using the metadata api when you deploy your you implementation (both objects and the code)

zeezackisbackzeezackisback

How do I know which is the right version? I got Eclipse 3.4.2

 

 

BulentBulent

Force.com IDE is not compatible with eclipse 3.4. You can check the details here 

Message Edited by Bulent on 06-01-2009 10:02 AM
MycodexMycodex

I know this post is old but better late than never since I regularly see unfinished threads on this forum.

 

I ran into a similar issue. My output was identical. I've deployed using Eclipse countless times but I just updated Eclipse. The issue was that I was trying to deploy using the Navigator view. Switching over to the Package Explorer view solved my issue.

 

The Package Explorer view can be enabled by clicking

Window | Show View | Package Explorer

 

Both views are needed when using Eclipse. Package Explorer will deploy changes while Navigator should only be used to delete files off the local machine. I believe if you try to delete a file through Package Explorer that you are effectively deleting them off the server as well.

This was selected as the best answer