{"id":131,"date":"2013-11-22T14:40:45","date_gmt":"2013-11-22T22:40:45","guid":{"rendered":"http:\/\/www.bridgefarmconsulting.com\/blog\/?p=131"},"modified":"2013-11-22T14:40:45","modified_gmt":"2013-11-22T22:40:45","slug":"use-the-new-force-com-cli-for-a-clean-quick-start","status":"publish","type":"post","link":"https:\/\/www.bridgefarmconsulting.com\/blog\/use-the-new-force-com-cli-for-a-clean-quick-start\/","title":{"rendered":"Use the New Force.com CLI for a Clean Quick Start…"},"content":{"rendered":"

Just got back from another exhausting by very fun Dreamforce!<\/p>\n

If you were at the Dev Keynote, you would have the seen the legendary Dave Carroll<\/a> demo a new Command Line Interface<\/a> for Force.com. I have been trying it out this morning (thanks to Mike for his help<\/a> getting me up and running!) and realized it is the perfect tool for something I seem to spend my life doing – cleaning up a new dev Org. I fire up new orgs every week, and I am always having to clear out the sample custom fields before I can get started. Why not just leave them there you ask? Soooo easy to accidentally include them in a managed package – and once there, no going back!<\/p>\n

But with the CLI, you can just run a simple script to do that. For now, you first have to delete some references to those fields. You can probably do this via the Metadata import as well, but until I work that piece out, you still have to do the following:<\/p>\n