Hi Jeane,

Although it is possible to change field types, I would not recommend changing the field type for a field where there is already previous data entered. For example, if the opportunity name is currently a text field and there are already opportunities in the system, then changing the field type to a picklist would not be advisable. 

You may also want to check if there are workflows in place that use the field as a criteria or online forms mapping to that field. 

Thank you,

Karen Guanzon

There is not much historical data in the the system related to the particular field I am talking about.  I would potentially see a solution as printing a report on the current data.  Changing the field type, then re-entering the historical data based on the new field type.  What are your thoughts?

There is not much historical data in the the system related to the particular field I am talking about.  I would potentially see a solution as printing a report on the current data.  Changing the field type, then re-entering the historical data based on the new field type.  What are your thoughts?

Hi Jeane,

My apologies, I forgot that standard fields are part of a managed package which means you cannot edit them. So what you would have to do is to create a custom field that you can use instead.

For opportunities, a few things you need to consider:

1. If you create a custom field, the 'Convert to Transaction' button that launches a Visual Force page is not designed to pull from the custom field you create and it is currently not possible to modify the Visual Force page.
2. The 'Proposal' field on the Transaction record is a look-up to Opportunities but is designed to display the current opportunity name field and not your custom field.

At this point, I recommend leaving the opportunity name field as is. Is there a particular reason as to why you wanted it changed to a picklist?

Thank you,

Karen Guanzon