Please Login with your Salesforce ID to post, promote or comment.
Salesforce IdeaExchange
FAQs | Terms of Use7408 Ideas; Promoted 154855 Times; 14448 Comments.
- Suggest a New Product Concept
- Promote Ideas That You Want to See Developed
- Discuss With Product Managers and Other Users
- See What We Are Planning To Deliver
Customization Comments
| Customization Ideas
|
Force.com Platform Comments
| Force.com Platform Ideas
Cross Object Workflow
Do not hard code the Object (see above image) when creating Workflow Field Updates. Allow administrators to choose a field to pass based on a relationship (lookup or master detail). For example, a Workflow Rule based on Case would be allowed to have a Workflow Field Update change a Contact field for the Contact record associated with the Case.
|
WrogWrog 03/20/07 |
Even if this was only restricted to parent or child objects, this would be a huge step forward, eg if a change is made to an opportunity product, it could update a field in the parent opportunity, or if a field on the opportunity changes, another field in all the products could be changed. |
|
dave_k 04/02/07 |
I'd agree with this one. Our specific requirement is that Accounts will have a number of incidents they can raise as a case. Each time we raise a case, we want to decrement the incident count and be able to send an outbound e-mail to the account owner if the incident count reaches zero. |
|
BradR 04/18/07 |
I can think of so many problems that cross object field updates would fix for me! This would be a great idea! |
|
BVanderzanden 04/30/07 |
Another thing this would allow is to change the "status" of a case if anyone but the owner has updated it. Our agents use a custom status field to track the current state of a case (waiting on customer, researching, etc). It would be nice to be able to have this status automatically set to "Action Required" or some-such when anyone but the owner updates the case or any related field under the case. |
|
holland44 05/01/07 |
Yes! this would be very helpful |
|
rhythmanx 05/15/07 |
Oh yeah, I've got workflow waiting for this one. |
|
loris 05/17/07 |
Yes, yes, yes - this would be wonderful! |
|
BrandonLA 06/01/07 |
This seems like an obvious part of workflow management. I would like to change account information based on activities. |
|
Letty 07/30/07 |
Yes, please add this feature - this would help me with current workflow. I need a way to populate custom object fields when a change is made in a standard object's fields. |
|
sepost 09/10/07 |
I would *LOVE* to update across objects!! |
|
hdecora 09/17/07 |
This functionality is vital and seems it would be a relatively easy fix - given that we are working with "relational objects"! |
|
pusherman13 10/04/07 |
Merged Idea
originally posted 09/13/07
Cross-Object Field Updating and Validation
It would be great if SF would allow us to perform cross object field updating and validation..
Example: If field A on Object X is updated, then updated field B on Object Y. or You cannot save record A on an object unless field x on another object has been updated. |
|
maryone 10/04/07 |
Merged Idea
originally posted 04/17/07
workflows with update fields - across tabs
Workflow / Alerts / Approvals
field update issue OR Formulas Currenlty it is not possible to reference field information across objects with standard salesforce.com functionality. Therefore, it would not be possible to update field information on one object, based on field criteria in another object. I was wondering if the possibility of using either workflows or Formulas is possible accross tabs. I mean for example with a field contained in the "Account" Tab and another in the "Project & Issue Management" Tab. Thanks, |
|
evolv 10/04/07 |
Merged Comment originally posted 05/15/07 |
|
Nathalie_Cloix 10/04/07 |
Merged Idea
originally posted 01/17/07
Field Update Across Objects
We should be able to create Field Updates across objects.
For example, if a product at the product/line item level is a subscription, then the opportunity type should be "Subscription". Currently, we can set a Field Update using Opportunity information or Opportunity Product information, but not across the two objects. |
|
pwatson 10/04/07 |
Merged Comment
originally posted 03/06/07
We want to update an Account field once an opportunity has reached a certain stage to remove user error or forgetfulness.
|
|
Mattybme 10/04/07 |
Merged Comment
originally posted 07/30/07
We want to be able to have information that is processed in a contact to update in accounts and oppurtunities etc.
|
|
NPM 10/16/07 |
We need to do a field update to update a custom object record with data (custom and standard) from the Account it is related to. |
|
chamundi_v 10/24/07 |
hi. how do i add the extra drop down list Field Value to Pass in the workflow field update Edit page. |
|
cmh 11/06/07 |
I have many more uses for inter-object workflow than I do for intra-object workflow. This would be sweet. |
|
peter_middleton 11/09/07 |
We are an Appexchange partner that develops and markets a product called Optimizer providing an on-demand business process management solution. Cross object workflow is one of the key features of our solution. Optimizer can virtualise all of the objects in your SF environment and other enterprise applications and make them available for validation and update as part of an end-to-end workflow/business process. Visit our site at www.synchosoft.com and click first on the Optimizer flash link |
|
heidi_drapeau 11/15/07 |
Has anyone been able to update lead status to contacted (or something of the like) based on last activity....NOT last modified date? |
|
doncarlito 11/20/07 |
Salesforce are half there with Winter 08 - you can update fields on child records with data from a parent object, getting it to work the other way around would be great, e.g. when a the first opportunity closes at an account, update the status of an account from prospect to customer |
|
bhughes 12/12/07 |
With winter '08, as doncarlito mentioned, you can update a child with data from the parent object. I have yet to actually see the use of this though. It's the child to parent that I'm looking for! |
|
olkeith Jan 22 |
This works for copying needed fields from a parent record down to the related record, but there is one limitation that i am severely hitting. I cannot update a picklist with the value of another picklist. This can be extremely limiting. |
|
e36mpower Jan 25 |
This functionality (parent child or cross object field updates) is badly needed. It would be a huge improvement to the workflow functionality. It is disapointing that there has not been any response from SFDC based on the current vote count for this request. |
|
jorgerbaker Mar 4 |
This could be a useful feature in regards to linking objects as well (not parent/child) and being able to do mid-level joins. Example would be a referral linking object between two+ distinct contact databases and opportunities and once the opportunity was marked 'closed won' the linking object would also have 'closed won' marked for use in related lists and other reporting. |
|
jason_w_gardner Mar 30 |
This could be very useful for our organization as well. Being able to update a field through a workflow rule on any lookup object seems like it would be relatively simple to do, and a logical progression from what exists today. Locking the object doesn't make much sense at all. |
|
bhughes Apr 1 |
I'm confused also as to why we cannot update and populate Lookup fields, or one picklist with a value of another picklist. |
|
kjoseph Apr 2 |
Changed status to Ideas Under Consideration. |
|
TheBoot Apr 22 |
Thanks for changing it to under consideration. I really hope that this will become available soon. I want to put in my vote for the Updateing from Child to Parent part. i really need that. |
|
hr May 9 |
Yes, this would be useful. |
|
joneuropean May 9 |
I need to reference the Opportunity Amount in a report on Activities. This will show the number of meetings/calls needed to close a certain type of opportunity. This Cross Object release seems to be the answer. I have tried three times with the support staff at salesforce and no-one even mentioned that this functionality wasn't yet available. Come on, hurry up! |
|
joneuropean May 9 |
I need to reference the Opportunity Amount in a report on Activities. This will show the number of meetings/calls needed to close a certain type of opportunity. This Cross Object release seems to be the answer. I have tried three times with the support staff at salesforce and no-one even mentioned that this functionality wasn't yet available. Come on, hurry up! |
|
angie_mehsling May 12 |
I am new to workflows and have had them in my upgraded edition for about a week. I found three cases where I wanted field updates to happen when a drop down value in another object changed to a certain status. In ALL three cases I needed to base my updated field on a different Object. For example, I want to Update my Account with a certain internal code once an opportunity is 'Closed Won', but I can only associate the workflow with the Opportunity Object. In my world, MOST instances would involve cross object workflow . |
Please log in to post a comment
last 100 promotions:
- kek
- JudiS
- collabengine
- motu
- albertokite
- 06/30/2007_0:36
- lcollz
- mcronin
- lez01
- sdunham
- mehdi_farbod
- CSchares
- berger
- montumavi
- jcoppedge
- pepsigirl
- PEHDK
- sbridges
- daringrad
- solcomsf
- angie_mehsling
- dlange@centerstance.com
- andrzejw
- aslutsky08282007
- Taylor_Smith
- manishdhupar
- susan_kolb
- steve_molis
- sfranklin01162008
- joneuropean
- hr
- jp_seabury
- susieb
- KT-MSMITH
- bw77
- Linda614
- jrivard11022007
- DenverDon
- beckas
- hollyfaulkner
- CRMSystemAdmin
- Datanatrix
- tbc
- slainte
- mwyatt
- acv
- alexb
- avictorio
- SFDC2admin
- Eirik
- Gracie
- axeleik
- sriramvsv
- aw1sfdc
- erin.cox
- danbig
- AustinGirl
- EmilyLiggett
- Kringo
- nriitano
- wj
- rsplastic
- monicag
- darrellg
- scottcparker
- CraigAllen
- nyccrm
- bvass
- robertc
- isaha@navatargroup.com
- hpci
- cresn
- ChrisMcL
- sausalitoadmin
- megar@apprivo.com
- aine
- dbmadp
- sunedlm
- CMSBrian
- cyndi_linkous
- kmulcahey
- pj100
- cerijones
- Sharifa_Shafi
- dcoons09282007
- ludo75
- wylieatworknz
- JDenis
- Amu
- paul_weeden
- tunedog
- new_user
- testerforce
- md
- CThompson
- Pepe2007
- cjones613
- mauricio_parra
- Brian00001
- dwachtel
POST IDEA
TOP USERS
Also currently there is ability to override the New, Edit and other buttons. But we do not have the ability to modify the logic behind the Save button.
We need the ability to modify the logic of the Save button , which will enable us to update the fields across objects. I understand this feature will be available through Apex Code.
Does anyone know when this feature will be released in the Enterprise Edition so we can attain our goal of updating fields across objects?