<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Migrating Salesforce.com Configurations  with the Metadata API &amp; Force.com Migration Tool</title>
	<atom:link href="http://blog.jeffdouglas.com/2008/07/15/migrating-salesforcecom-configurations-with-the-metadata-api-forcecom-migration-tool/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.jeffdouglas.com/2008/07/15/migrating-salesforcecom-configurations-with-the-metadata-api-forcecom-migration-tool/?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=migrating-salesforcecom-configurations-with-the-metadata-api-forcecom-migration-tool</link>
	<description>Get your head out of your #@! and into the clouds!</description>
	<lastBuildDate>Wed, 08 Feb 2012 07:57:55 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: Jd</title>
		<link>http://blog.jeffdouglas.com/2008/07/15/migrating-salesforcecom-configurations-with-the-metadata-api-forcecom-migration-tool/comment-page-1/#comment-987</link>
		<dc:creator>Jd</dc:creator>
		<pubDate>Sat, 10 Jul 2010 19:34:35 +0000</pubDate>
		<guid isPermaLink="false">http://jeffdonthemic.wordpress.com/?p=86#comment-987</guid>
		<description>I&#039;ve never seen this document but would love to.  Was it released?</description>
		<content:encoded><![CDATA[<p>I&#8217;ve never seen this document but would love to.  Was it released?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: &#187; Adding multiple fields via metadata (The Enforcer.net, a force.com blog)</title>
		<link>http://blog.jeffdouglas.com/2008/07/15/migrating-salesforcecom-configurations-with-the-metadata-api-forcecom-migration-tool/comment-page-1/#comment-16</link>
		<dc:creator>&#187; Adding multiple fields via metadata (The Enforcer.net, a force.com blog)</dc:creator>
		<pubDate>Mon, 25 May 2009 01:54:29 +0000</pubDate>
		<guid isPermaLink="false">http://jeffdonthemic.wordpress.com/?p=86#comment-16</guid>
		<description>[...] Jeff Douglas&#8217; blog post on Migrating Salesforce.com Configurations with the Metadata API &amp; Force.com Migration Tool [...]</description>
		<content:encoded><![CDATA[<p>[...] Jeff Douglas&#8217; blog post on Migrating Salesforce.com Configurations with the Metadata API &amp; Force.com Migration Tool [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jeffdonthemic</title>
		<link>http://blog.jeffdouglas.com/2008/07/15/migrating-salesforcecom-configurations-with-the-metadata-api-forcecom-migration-tool/comment-page-1/#comment-15</link>
		<dc:creator>jeffdonthemic</dc:creator>
		<pubDate>Tue, 05 May 2009 16:50:39 +0000</pubDate>
		<guid isPermaLink="false">http://jeffdonthemic.wordpress.com/?p=86#comment-15</guid>
		<description>There are alot of thing you CANNOT do with the Metadata API. However, Salesforce.com will not release that list. For instance, cannot migrate standard picklist values, only custom ones. We are finishing up a release management document that we&#039;ve put together with Salesforce.com&#039;s input and I&#039;ll release that soon. We are also working with the Metadata team and providing them input on what we think should be available functionality with the Metadata API. There is alot of work to be done there.</description>
		<content:encoded><![CDATA[<p>There are alot of thing you CANNOT do with the Metadata API. However, Salesforce.com will not release that list. For instance, cannot migrate standard picklist values, only custom ones. We are finishing up a release management document that we&#8217;ve put together with Salesforce.com&#8217;s input and I&#8217;ll release that soon. We are also working with the Metadata team and providing them input on what we think should be available functionality with the Metadata API. There is alot of work to be done there.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bhavana</title>
		<link>http://blog.jeffdouglas.com/2008/07/15/migrating-salesforcecom-configurations-with-the-metadata-api-forcecom-migration-tool/comment-page-1/#comment-14</link>
		<dc:creator>Bhavana</dc:creator>
		<pubDate>Wed, 29 Apr 2009 21:52:18 +0000</pubDate>
		<guid isPermaLink="false">http://jeffdonthemic.wordpress.com/?p=86#comment-14</guid>
		<description>Hello Jeff,
Thanks for this excellent tutorial! I&#039;m a SFDC
newbie and I&#039;m dabbling around with the metadata
api. I want to push a picklist field &amp; its
values from one org to another. My question is:
Is it possible to push field dependencies,
validation rules, controlling options (BASICALLY
everything attached to this picklist field,
and not just the picklist values) from one
org to another?
(Because when I use the Compare With each Other)
option, I only see the picklist and it&#039;s
corresponding picklist values to move b/w the
orgs, I dont see the other items: field
dependencies etc). I would greatly appreciate
any feedback!!

Thanks again! -SFDC Newbie</description>
		<content:encoded><![CDATA[<p>Hello Jeff,<br />
Thanks for this excellent tutorial! I&#8217;m a SFDC<br />
newbie and I&#8217;m dabbling around with the metadata<br />
api. I want to push a picklist field &amp; its<br />
values from one org to another. My question is:<br />
Is it possible to push field dependencies,<br />
validation rules, controlling options (BASICALLY<br />
everything attached to this picklist field,<br />
and not just the picklist values) from one<br />
org to another?<br />
(Because when I use the Compare With each Other)<br />
option, I only see the picklist and it&#8217;s<br />
corresponding picklist values to move b/w the<br />
orgs, I dont see the other items: field<br />
dependencies etc). I would greatly appreciate<br />
any feedback!!</p>
<p>Thanks again! -SFDC Newbie</p>
]]></content:encoded>
	</item>
</channel>
</rss>

