Salesforce IdeaExchange
- then -
Sales Force Automation Comments
| Sales Force Automation Ideas
|
Applications Comments
| Applications Ideas
Clone - Ability to Control Which Fields are Cloned
I would like the ability for an Admin to control which fields are copied when an object is cloned.
E.g. for Opportunities, I don't want the 'Opportunity Status' copied. Even though it's mandatory, by copying it the user is not prompted to update it. Typically users are cloning existing opportunities to new opportunities and for busy sales guys it's easy for them to miss this out.
If the Admin could set a flag on the field to say it should not be copied when an opp is cloned, the user would then be prompted to update this mandatory field.
This could be applied to many other fields of course.
|
RK 06/25/07 |
This is a great idea. To relate it to contact records - my users often time clone contacts, thereby cloning the birthday of the original contact, the spouse of the original contact, etc. Under no circumstances should those fields be cloned. It would be great to turn it off for them. |
|
brailm 07/25/07 |
I am struggling with this myself. I am close to turning off the ability to clone contacts because fields that should not be cloned are cloned. We have created a set of workflow rules that clears out certain fields when opportunities are cloned, but I can't access a multi-select picklist field that controls which contacts are sent to our backend systems. Major issue for us (costs several hours each week to correct). |
|
TDP314 01/31/08 |
It would also be nice to control related objects to be cloned with the record. Or default the cloning to include the object at all times. ex. we require products to calculate the total amount on a deal. When cloning, we would like it to default to "Clone with products". If the deal is cloned without the products, the amount field should not be copied from the clonee. |
|
awprxdan 05/29/08 |
Good idea! I also need to clone w/o copying a status field, or - a trigger on clone where I can set the values of fields. |
|
mnorth 08/06/08 |
Great idea. When cloning opps it would be great if we could not clone the status. However, I do want to clone the territory, contact roles, and sales team. |
|
parnelli 08/19/08 |
The lack of ability to control which fields are cloned is a huge omission within Salesforce.com. Even ACT allows you to pre-determine the exact fields to clone/duplicate. I'm pretty shocked that Salesforce doesn't have this capability. It's ridiculous for so much "contact-specific" information to be cloned (name, title, prefix, suffix, cell phone, home phone, home address, ad infinitum). |
|
nayoub 08/25/08 |
we should be able to control what is cloned. for instance, some of my users clone each other's contacts - but the owner name is cloned. so ultimately they're just creating a duplicate contact for the original owner. in my organization, i'd like to default the owner name to be the person who is cloning the contact, not the original owner. i'm sure this isn't the case for all organizations, so I really think we should be able to manage this ourselves as admins. |
|
heyjenromano 09/09/08 |
We constantly have to look for ways around cloning certain fields on all objects. It would be nice if it were just a list of fields with a checkbox (similar to history tracking) on which fields clone and which fields don't. |
|
Hayley 09/18/08 |
My company is struggling with this as well. Cloning on both Leads & Opportunities, where fields are not being updated/changed. We would appreciate the chance to identify what fields need to updated prior to saving the new item. - Something like making specific fields blank, once cloned, and then if those are required fields, the user could not save the new object, until new information is updated. |
|
ben_hizak 10/08/08 |
Hey guys. Great Idea and I promoted it, but would someone please tell me how you are currently dealing with the problem? Thanks |
|
WrogWrog 10/09/08 |
I currently deal with this by hoovering up the errors later! Clone is currently the ultimate love/hate feature - saves us loads of time and causes all sorts of mistakes. It would help if we could have and audit trail, as in http://ideas.salesforce.com/article/show/70523/Record_the_record_cloned_from_... |
|
brightgenrichard 10/13/08 |
I'm working on a solution to allow Opportunities to be cloned with its products, and allow you to reset the Stage (among other custom fields). I'll keep you posted when it's ready. |
|
VentyxAdmin 12/16/08 |
I agree. We have several fields editable only to certain profiles (ie. our Legal Dept) due to workflow rules and would like to prevent these specific fields from being copied when we clone an opportunity. |
|
getitdone 12/16/08 |
This would greatly enhance the adaptation of SF across departmetns in our orgainization. The current limitation is a drawback to SF further use of sub lifecycle type processes within an opportunity - such as contract processing, quote preparation, proposal responses which may be started and stopped several times within the life of an opportunity and certainly won't carry forward in a opportunity where you are renewing or upgrading the offering. |
|
aberry 12/17/08 |
The ability to limit certain fields from being cloned is becoming a high priority within our organization, specifically in Sales, Legal, & Accounting. To be able to have a simple check list of fields, specifically for opportunities that you may select for cloning is an imperative need. We have multiple workflows & notifications established for opportunities as they're created & updated. However whenever someone clones an opportunity, all fields with existing data gets copied over to the newly cloned opportunity and triggers & email notifications are executed automatically. This skews dashboards and reports specific to other departments that play an active role in the opportunity lifecycle process (i.e. Legal). |
|
jeffmartin Yesterday |
Why has SF not commented on status of this? It is a love/hate for us also, clearing fields is taking as long as creating new. |
track comments for this idea
Please log in to post a comment
recently promoted by:
- jsmengel
- dgimbert
- jeffmartin
- alex.lares@v2sa.com
- aberry
- getitdone
- VentyxAdmin
- maryachuong
- CKA
- louisamaskell
- DBMSRock
- TehNrd
- esa
- brightgenrichard
- ben_hizak
- Hayley
- JoAnnCulbertson
- suro1us
- mpdrsn
- drewalexander
- heyjenromano
- andrew@asa
- Mhagey
- foreward
- crispy
- tecanj
- pierrepannunzio
- debbiebowers1
- ricu1ch
- kelley_oberhart
- parnelli
- drewpup
- Letty
- mnorth
- shaunovision
- annray
- susana_nts
- david_hays
- Barb_Rheaume_@_MTS
- awprxdan
- blackCompG
- craskulinecz
- roufle
- TDP314
- adept4
- datarzan
- e36mpower
- mlee
- nc_user
- alliforce
- wennerj
- brailm
- JustinClarke
- Violam
- jet
- Marq
- WrogWrog
- NPM
- Kringo
- RK
- msnowden213
- 4_Hub
- ErikO
- rpr2
- berger
- nayoub
- LM
- kww
- Leyna
- KevinEdelmann
- MikeArthur
POST IDEA