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
Sree007Sree007 

Need Installation Help

Gurus,

This might find silly, but I could not find this information anywhere.

We have deployed custom components A, B, and C

I created a new Sandbox (Full Version).

Created new custom component D in Sandbox, with references to Components A, B and C (and vice versa)

When I try to upload this new component D, it gives me all the components A, B and C inclusive with all the types (fields, workflow etc). Now the problem is when I try to upload and install in my production, it states all the components exist (or at least for A, B and C) because of the relationships and lookups and existing fields. I know they exist, but how do I ignore or tell package to update instead of saying "This is a brand new component" in the installation notes. This package automatically includes all the fields form component A, for example, even though there are no changes to these fields.

 

I really do not want to create this whole package in production. Is there a way to deploy versions of components, instead of full version of all related components?

 

Thanks in advance

Sree

JonPJonP

You cannot use packaging for this scenario.  Packaging is for independent software vendors (ISVs) to distribute applications to their customers on the AppExchange.

 

What you want to do is called metadata migration.  You can do this using the Force.com IDE (for Eclipse) or the Force.com Migration Tool (for Apache Ant).

 

 

Force.com IDE

http://wiki.developerforce.com/index.php/Force.com_IDE (link)

 

Force.com Migration Tool Guide

http://www.salesforce.com/us/developer/docs/daas/index.htm (link)