Package to publish an custom field defined on standard module

[tss]

hi,
i dont know how to create a package who publish a custom field defined on a standard module.
By example, i've defined a new field on the Opportunity module in a test environment, and i would like to publish this new field in a Production environment. Can you help me to defined the manifest file ?

Thank you in advance for your help

[salesagility]

Just so that I understand ... you want to create a custom field on a test server, then package it up and deploy it to a production server?

[tss]

Yes, i have created a custom field on Opportunity module on my test environment, and i want deploy this on my Production environment.

[tss]

I'm surprised that nobody has encountered this problem.
How do you upgrade your production environment from your test environment ?

[salesagility]

It's just not the way that sugar works ... you can build a custom module and export it for deployment into another environment, but not custom fields.

But if your production and test servers are in sync, then if it works on your test server, then simply recreate it on production.

[ravensorb]

Hmm, this is a little concerning to me as well. So how are you supposed to deploy customizations to the standard modules?

Example Scenario:

I am creating a custom CRM solution for a dog rescue group. I need to create several custom modules (for the dog, donations, applications, etc) and then I need to add several custom fields to some of the default modules (contacts, events, etc). For example, I want to add a "contact type" to indicate if the contact is a volunteer, adopter, or fosterer. Now once this change has been made and I have tested it (and the changes to the details and edit screens) how am I suppose to package it up so that I can deploy it?

[roblaus]

Of course you can export customizations. The front screen in studio does have a button for it.

But: Don't expect it to be error free since not even so called heroes know about its existence. And: It's indeed not the correct (planned, intended...) way of doing it. You should reproduce your customer's environment (development, test) or create installable modules even for single fields (which is an overkill but possible).