Salesforce IdeaExchange
- then -
Customization Comments
| Customization Ideas
|
Force.com Platform Comments
| Force.com Platform Ideas
Allow page layouts to display fields from related objects
For usability and productivity reasons, it is often useful to be able to see parent fields and child fields on the same detail page. For example, on a Contact detail page, it may be useful to see Account fields. Or display an Asset Serial Number (custom field) on the Case Page.
|
GroovyJack 10/10/06 |
Or more info about Account and Contact on the Case page - I agree. |
|
Pramod 10/11/06 |
Agreed .. This is the feature salesforce is lacking big time. Currently object can display only Key Field. We ended up creating duplicate fields on Accounts and opportunity. This also creates data maintanance issue. Rather then duplicating , I prefer displaying the Accounts fields on opportunity. |
|
mankind 10/11/06 |
Definately. If you go deeper you will see that the lack of this feature affects two areas: 1. Reporting 2. Alerts If you reference a custom object on an opp for example, you can access the 'related' information on the object or the alert thus causing workarounds and endless compromise. |
|
jgreene 10/11/06 |
This sounds like some of the functionality that's in the Support Console beta. Definitely very helpful for people such as support staff, who need to quickly pull together lots of related information onto the same screen. Ever called a support number for a big company and had the support rep say "Oh hold on, that information is on another screen." AARGH!!! |
|
fifedog 10/11/06 |
However does the new 'desktop' work for this? You can now display other related information on the same screen? |
|
FeatureReq 10/12/06 |
This is a key feature to our business model, as we need to see detailed information about our clients from the opportunity screen in order to process the transaction faster. Currently, we have to have our reps perform additional click steps in order to track this information. The new Business Web desktop would work for this issue, but ideally you would have the option to use the traditional layouts with referenced fields as well. |
|
cluvara 10/13/06 |
Yes, most definitely need this! I think it would be better w/o the pop-up however. Displaying the fields on the page would make more sense I think for user experience. |
|
EricB 10/13/06 |
What if you could hover over the Account Name on the Contact page and see a pop-up hover with more fields from the Account record? Would this cover the need, or would you rather see the Account fields directly on the Contact page without having to take some action? |
|
ErikM 10/14/06 |
Eric, this would be a very nice extra feature, and hopefully the planned enhancements to custom formulas will also take care of the more immediate need to provide specific details of a related object, provided that they can drill into any related record, not just parent and child records. |
|
Pramod 10/16/06 |
Eric, Popup Hover is a good idea but not workable all times as these days most of the users have Popup blockers etc installed...And one can't really have a control of user machine I personally would prefer having the actual information on the page. Pramod |
|
NDeveloper 10/17/06 |
Related lists already allow child data to be visible on a parent record, the problem is showing parent data on a child and in particular indireclty related data in a many to many relationship where all you can show is the ID and not the related data. For instance we have a many to many relatioship between Employee and Case and would like to show the Employee name on the related list but cannot because the ID of Employee is Employee ID. |
|
loleary 10/17/06 |
If the pop-up hover would be a good start, assuming it is not a pop-up window but an actual script driven function of the object's page. I think it may still be necessary for a related object's field to be available in page layout and, if not already, e-mail template fields. |
|
mscotton 10/23/06 |
Thanks for all the great feedback. This idea is planned for a future release, and your input will influence our design decisions. Check out vanHusen's posting for a visual and implementation .http://ideas.salesforce.com/article/show/27800 |
|
kcb 10/27/06 |
Im actually researching this issue now and came upon this. Im excited to hear that this will be available in 2007. I would think however that there must be a way now to do this. Does anyone have any workarounds to suggest? My customer is specifically lookin to display a lot of customer information on the case layout page as it pertains to equipment and such. Please let me know. |
|
ErikM 10/27/06 |
kcb, with Winter '07 you'll be able to add custom s-controls to the fields' sections. So, if you can create an s-control that pulls the data in the background - and display it using sfdc stylesheets - and add it to the page layout, then you can mimick the behaviour of related fields right away. I have tried this out in the pre-release system, and it worked just fine. Best practise is to pull all the data at once to save time, but I'm not sure how it will look if you want to span two columns (I only tried 2 fields in a one-column section). Formatting is a bit tricky, but you'll figure it out. |
|
dgildar 10/27/06 |
Agreed .. This is a must-have feature missing in salesforce. The absence of this feature forces denormalized data for expendience. |
|
mscotton 10/31/06 |
What ErikM suggests is possible in Winter '07. Another approach is to use the Business Web Desktop console to display the Case information and related information (for Account, Contact, any related object). Check out this post for details: http://ideas.salesforce.com/article/show/17798 |
|
Stevenn 12/13/06 |
Yes, this idea would save time and re-entry |
|
tl 01/15/07 |
I would like this idea promoted as well, but instead of the last sentence in the original post, I would like that sentence to be changed. "Or display an Asset Serial Number (custom field) on the Case Page." Instead of a custom field, I would like the standard field of "Serial Number" to show on the Case page. Why would you want a custom field of Serial number when a standard one called Serial number already exist? |
|
guinnessisgood 02/14/07 |
I highly support this concept and I think a good way to control the hover data would be for there to be a setup somewhere for a "Hover Layout." Not that it has to be different by profile, but as long as you today setup the Console mini page layouts by profile, why not? I can see why support users would have a different interest in contact details that you hover over than would a sales person. This also narrows the focus of the AJAX call. If you need only a little data brought back, that's what you get and your call is efficient. What this idea (hovers) would do is allow "nearly drilling" into data in any form, whether through standard interface or in the Console. If EricB can comment on when this type of functionality is anticipated, that would be great. 146? 148? |
|
MEast 03/12/07 |
I agree 100% |
|
RobIrving 03/12/07 |
It is not so much a matter of being able to _see_ the information from a different table, but the ability to cross-populate. Sales wants to know if Support upgrades a customer to a new product version (information we store on the account currently, but resolve in support), and Support wants to know all of the data that is gathered by Sales when a customer joins us. Being able to see the data -- in a console, for instance -- is not much of an advantage over using a separate support software solution. It still requires us to duplicate all of that data in two tables in two locations, and introduces more possibility for discrepancies between the two. |
|
James_McGill 03/14/07 |
Merged Idea
originally posted 10/25/06
Display information from a reference
I am using the Project module and would like to select a contact to whom the data will be delivered (separate from the client project manager). While I can add the lookup, I cannot display any information about the contact on the page. Please add the ability to display selected information from a lookup object.
|
|
mscotton 03/14/07 |
Merged Comment
originally posted 10/31/06
Changed status to Duplicate.
|
|
Kingsley 03/14/07 |
Merged Comment
originally posted 03/14/07
Changed status to none.
|
|
KateReilly 04/10/07 |
We would like the ability to added Account information to the cases layout. We have a lot of customer environment specific information that we track in our Account record and would like to be able to view that information within the support Case. |
|
MrB 05/02/07 |
I would just like to be able to display any given field from the custom lookup. A syntax such as {!asset.serial} or {!product.product_family} as a custom field call would be plenty sufficient, right? Since it's solely for display purposes and not editing, I would imagine the impact of such an enhancement would not be very significant, but then I'm no expert on this... yet! Hope something along these lines is planned soon! As a thought, could something like this be accomplished using s-controls? |
|
JJohnson 05/29/07 |
This will be huge & will eliminate several dupe fields I have had to create. This will improve the overall integrity of our data. |
|
PatientKeeper 06/15/07 |
Merged Idea
originally posted 10/10/06
Display Any Field of a Related Object (duplicate)
Note: This is a duplicate of another idea.
Cast your vote for this feature here: http://ideas.salesforce.com/article/show/22246 ------ When setting up Page Layouts it would be greatly beneficial to display any fields from a related object. For example, when setting up the Page Layout for Cases, we would like to be able to display ANY field on the related Account object, not just the Account Name. |
|
sandrags 06/15/07 |
Merged Comment
originally posted 10/14/06
Yes, very important for user experience. Needed for all lookups, from/to any objects, custom or standard
|
|
vanHusen 06/15/07 |
Merged Idea
originally posted 10/23/06
Show Information of created Custom Fields in other Tab / Section (duplicate idea)
It would make sense to show a Custom Field which was createt e.g. in an Account in another section e.g. in Cases.
It is not possible to show information filled in at a custom field at another page for look up. I want to show my supporters a new field (Contract Penalties) which I created in the Account section in a case automatically after saving the case. New case => choose Contact Name => Account Name and Contact Details are shown after saving the case automatically. I want to show the created field belonging to the choosen account there, too. So the supporters have further information after choosing the account. The new field should be choosable at the Setup under the "Page Layout": Setup => Customize => Cases => Page Layout => Edit [A similar idea has already been posted: http://ideas.salesforce.com/article/show/22246 (Allow page layouts to display fields from related objects). Please vote for this idea under that posting. Thanks - Mary Scotton, salesforce] |
|
mscotton 06/15/07 |
Merged Comment
originally posted 10/23/06
Hi vanHusen,
Thanks for your posting -- this is a very powerful idea. It has already been getting many votes under this posting. http://ideas.salesforce.com/article/show/22246 (Allow page layouts to display fields from related objects). Please add your vote there. Thanks, Mary |
|
FICLSalesForceAdmin 07/06/07 |
The display is nice, but having parent object fields available for formula's would be very useful too. |
|
mscotton 07/06/07 |
Just wanted to let folks know that although we are not yet delivering this feature to directly add a parent field to a page layout, the hover functionality is coming in the Summer '07 release. With the hover detail feature, from the detail page for a record, you can hover on the link to any related object and see fields from that object. See this feature: http://ideas.salesforce.com/article/show/65763/SNIPS_of_web_links for more details and to comment on that functionality. |
|
CThompson 07/18/07 |
In response to the new "hover" feature being touted by SFDC posters: that is, indeed, a very helpful feature. However, it's a cosmetic feature that doesn't resolve the underlying relational database challenge that many people have mentioned. If related object fields were made available when creating formula fields, that would allow for some very useful functions to be performed (and would be more consistent with the expected functionality of an enterprise-class relational database). Example below. I'd like to create an "Amount after Discount" formula field on the opportunity object which performs the following calculation: {Opportunity.Amount} * {Account.Discount__c} Account.Discount is a custom field on the Account object that defines the discount percentage on file for that customer. Because Account is a lookup from the Opportunity object, we should be able to reference the related field in an Opportunity formula field. |
|
Donovan_Kruger 08/03/07 |
Not only should the field values of related objects be displayed in the detail page, but they should also be available for use in Communication Templates. For example, if I am triggering a workflow alert notification from a custom object that has a lookup to Product, I should be able to include field values from the Product in my communication template. Currently, this is not possible. |
|
fjw 09/13/07 |
I would take this a step further. Our use case stems from having a large number of our business units in the same salesforce instance and running out of custom fields. By allowing us to display (and edit) a related object on the same page layotu as the parent record, we could allow each business to extend the standard object independently while preserving the parent object for enterprise wide fields. In order to do this, the custom objects would need to be flagged to indicate if they had a 1:1 or 1:many relationship with the parent. The 1:1 related objects could be displayed and would perform the function that us old timers referred to as an extension table. |
|
Pepe2007 09/27/07 |
The ability to put fields from related objects on page layouts is something we have been in dire need of. Our Sales Reps Telmarket from their Contacts but to be efficient, they need Account information as well. Currently we need to create duplicate fields on both the Account and Contact objects which is time consuming and frustrating for our Reps. |
|
ElenaA 10/23/07 |
This becomes even more important as we try to analyze data without having to look at separate data tables. Our challenge is that I need fields from custom objects (child) to be displayed in the parent (Account object). Instead of requiring multiple entries, and instead of pulling 3 separate reports for analysis, it would be great if I can simply have the same data field show up in multiple pages. Then I can pull a single report and am not limited by the data structure limitations with custom objects. There must be an "S control" to do this. Why is this such a difficult feature to release? We spend so much time on work-arounds to accomplish the same thing. |
|
heatherp 11/28/07 |
Yeah we need to make this happening in opportunities as well. I really need to see what products are entered on an opp before approving and it would be nice to have that info listed in the opportunity approval page layout. |
|
schmeebs Jan 24 |
We desperately need this ability implemented in some way, even for 'trivial' use cases. For example, we need Opportunity.Amount to be replicated into a custom field on Contracts, which it seems should be as simple as point>click>select, but which seems to be very difficult for a small organization to implement at present. |
|
schmeebs Jan 24 |
To extend my previous comment, we also want/need to be able to compose reports and merge templates that can pull together info from different, but related, objects (including custom objects), that can be created/managed through a primarily point/click interface (at the very least, for an Adminstrator). |
|
atsdatajunkie Feb 20 |
I completely agree that we need the ability to link a field on one object to a related field on another object. As for the hover capability, that would be much more useful if it could be customized. Example - I need to see "Account_Number__c" on the Opportunity page, in addition to "Account Name." We have many customers with the same name, but different account numbers. I could squeak by if Account_Number__c was at least visible on the hover. But right now, all I can see hovering over Account Name is the Account Name and that Parent Name. That's really not all that helpful. I would *much* prefer to have the ability to repeat that field on the Opportunity page. But if the hover is supposed to be a solution, we need to be able to customize it, or we're no better off than before. |
|
Kringo Feb 20 |
Absolutely agree. Anywhere the Account lookup field is displayed there should be the account site information riding along with it. I am amazed that at there hasn't been any feature releases that have begun to address this |
|
Katmando Mar 7 |
This is similiar to my idea: http://ideas.salesforce.com/article/show/68096 |
|
mscotton Apr 12 |
Heads up that you will be able to do this using custom formula fields in Summer '08, but I am not going to mark this as "coming soon" because I still want to deliver the ability to do this without creating a formula field. Definitely check out the formula field solution in the meantime. |
|
Kringo Apr 14 |
Would the formula field update the value of the field if it were to change on the "Master" record or would this be similar to passing the values through a URL or SControl through a custom button? |
|
mscotton Apr 25 |
The formula field will just have a merge field in it that references the parent field. For example, a formula on Contact to display the Account phone number would just be: Account.Phone So, anytime you are viewing the formula field, you see the value that is currently in the parent field. The value is not copied (which is why this is a better way to do it than the current workaround of copying the values in a workflow field update). |
track comments for this idea
Please log in to post a comment
last 100 promotions:
- maksim
- ben_hizak
- pablo66
- ronald_helmstrijd
- mckeown
- grueser
- bdavis
- remmedical
- jasongwan
- liorm
- needsomechange
- merial
- markbrown
- drewalexander
- leosden40
- xroad
- Arnar
- larryssuggestions
- dklebanoff01312008
- taubium
- bao-long_nguyen-trong
- keano
- mcronin
- sh
- DoyleAtTSG
- KathrynHooper
- dcp
- jnugent
- marcus@the_'gan
- bw77
- karenstevens
- jsmengel
- vorno
- OH
- ajarosch@andersencorp.com
- kevinpa
- kleiserson10132007
- rsplastic
- pj100
- 03/1/2007_19:32
- EricG
- ludo75
- stevechadbourne03092008
- chrisnoesfdc
- crmddc
- hal1975
- crop1645
- pkim04152008
- gemma
- melmc8
- faquino101
- silvia@mm
- tasb
- bliss
- joseph_ferraro
- kai_harris
- Datanatrix
- MicaiahF
- Ben-Generate
- kshuk-canonical
- guillermosrs
- cases02072008
- dmrs22
- riptide
- pbueno11272007
- new_user
- paulMcGurn
- laguz
- mktgmgr
- sfdemo03262008
- ubbo
- scottcparker
- ronan
- HappyGirl1128
- awprxdan
- SheilaatUnivar
- almarcus
- htam
- jdev
- smithle
- kristinabeeby
- supportneeds
- nicekato43
- MSheridan
- stuart_bernstein
- andreas_krebs
- sal_caruso
- joshvh
- philk27
- big.t
- al2
- agluewvrs
- LikaB
- allmans1
- megachuckmc
- sunedlm
- Kenny
- Tek_Righter
- jayhunter
- bdaadmin03252008
POST IDEA