Driving adoption in Salesforce.com can be a full time job. The easiest way is to automate work for your users. Custom buttons and links take away some of the "busy work".
1. Custom Links & Buttons in Salesforce Sometimes users just need a button! Raleigh Salesforce User Group Amber Neill Salesforce.com Administrator iContact.com [email_address] [email_address] http://www.twitter.com/amber9904
2.
3. Adding a Report to an Account Business Problem: We have resellers who sell our widgets. We need to know how those resellers are doing. Who has account X referred? What is the total revenue account X has generated for us?
4.
5.
6.
7.
8. Adding a Report to an Account 2. Take the URL of the report https://na6.salesforce.com/00O80000003uWeY and save it off someplace safe. You'll need it shortly. The part of the URL after "https://na6.salesforce.com/" is the unique ID for your report. We'll use that to create our link.
9. Adding a Report to an Account 3. Go to Setup | Customize | Accounts | Buttons and Links 4. Click New 5. Give your link or button a Label, Name and Description 6. For this link we're going to choose Detail Page Link , we want it to Display in new window , and the Content Source will be URL. Now the fun begins...
10. Adding a Report to an Account 7. Remember that URL you saved off? Paste it in the Formula area 8. Take off the "https:na6.salesforce.com and add the following to the end of the URL: ?pv0={!Account.ClientID__c} This tells the link to add the merge field of ClientID as the first criteria for the report. (pv0 is the first criteria, pv1 is the second criteria, etc.) Use the "&" symbol between criteria if you're using more than one.
11. Adding a Report to an Account And here's your URL for your custom link: /00O80000003uWeY?pv0={!Account.ClientID__c} 9. Click Save Here's what the page looks like with all our settings...
If you don't have these permissions, you can use any button built by the person who does have the permissions....assuming you have permissions to the button!
1.) Create report 2.) Add criteria that filer on the ClientID, but leave the field blank 3.) Create a custom link on the Account object that is the URL of the report with the merge field for the ClientID NOTES: a.) Put the report in the appropriate folder so it is accessible to the right users. b.)
1.) Create report 2.) Add criteria that filer on the ClientID, but leave the field blank 3.) Create a custom link on the Account object that is the URL of the report with the merge field for the ClientID NOTES: a.) Put the report in the appropriate folder so it is accessible to the right users. b.)
1.) Create report 2.) Add criteria that filer on the ClientID, but leave the field blank 3.) Create a custom link on the Account object that is the URL of the report with the merge field for the ClientID NOTES: a.) Put the report in the appropriate folder so it is accessible to the right users. b.)
1.) Create report 2.) Add criteria that filer on the ClientID, but leave the field blank 3.) Create a custom link on the Account object that is the URL of the report with the merge field for the ClientID NOTES: a.) Put the report in the appropriate folder so it is accessible to the right users. b.)
1.) Create report 2.) Add criteria that filer on the ClientID, but leave the field blank 3.) Create a custom link on the Account object that is the URL of the report with the merge field for the ClientID NOTES: a.) Put the report in the appropriate folder so it is accessible to the right users. b.)
1.) Create report 2.) Add criteria that filer on the ClientID, but leave the field blank 3.) Create a custom link on the Account object that is the URL of the report with the merge field for the ClientID NOTES: a.) Put the report in the appropriate folder so it is accessible to the right users. b.)
1.) Create report 2.) Add criteria that filer on the ClientID, but leave the field blank 3.) Create a custom link on the Account object that is the URL of the report with the merge field for the ClientID NOTES: a.) Put the report in the appropriate folder so it is accessible to the right users. b.)
1.) Create report 2.) Add criteria that filer on the ClientID, but leave the field blank 3.) Create a custom link on the Account object that is the URL of the report with the merge field for the ClientID NOTES: a.) Put the report in the appropriate folder so it is accessible to the right users. b.)
1.) Create report 2.) Add criteria that filer on the ClientID, but leave the field blank 3.) Create a custom link on the Account object that is the URL of the report with the merge field for the ClientID NOTES: a.) Put the report in the appropriate folder so it is accessible to the right users. b.)
1.) Create report 2.) Add criteria that filer on the ClientID, but leave the field blank 3.) Create a custom link on the Account object that is the URL of the report with the merge field for the ClientID NOTES: a.) Put the report in the appropriate folder so it is accessible to the right users. b.)
1.) Create report 2.) Add criteria that filer on the ClientID, but leave the field blank 3.) Create a custom link on the Account object that is the URL of the report with the merge field for the ClientID NOTES: a.) Put the report in the appropriate folder so it is accessible to the right users. b.)
1.) new case record type for empowerment cases 2.) NOTES: a.) Who's going to handle these cases? Will a queue own them initially? b.)
1.) new case record type for empowerment cases 2.) NOTES: a.) Who's going to handle these cases? Will a queue own them initially? b.)
1.) new case record type for empowerment cases 2.) NOTES: a.) Who's going to handle these cases? Will a queue own them initially? b.)
1.) new case record type for empowerment cases 2.) NOTES: a.) Who's going to handle these cases? Will a queue own them initially? b.)
1.) new case record type for empowerment cases 2.) NOTES: a.) Who's going to handle these cases? Will a queue own them initially? b.)
1.) new case record type for empowerment cases 2.) NOTES: a.) Who's going to handle these cases? Will a queue own them initially? b.)
1.) new case record type for empowerment cases 2.) NOTES: a.) Who's going to handle these cases? Will a queue own them initially? b.)
1.) new case record type for empowerment cases 2.) NOTES: a.) Who's going to handle these cases? Will a queue own them initially? b.)
1.) new case record type for empowerment cases 2.) NOTES: a.) Who's going to handle these cases? Will a queue own them initially? b.)
1.) Determine what fields need updating. 2.) Map to URL for button NOTES:
1.) Determine what fields need updating. 2.) Map to URL for button NOTES:
1.) Determine what fields need updating. 2.) Map to URL for button NOTES:
1.) Determine what fields need updating. 2.) Map to URL for button NOTES:
1.) Determine what fields need updating. 2.) Map to URL for button NOTES:
1.) Determine what fields need updating. 2.) Map to URL for button NOTES:
1.) Determine what fields need updating. 2.) Map to URL for button NOTES:
1.) new case record type for empowerment cases 2.) NOTES: a.) Who's going to handle these cases? Will a queue own them initially? b.)
1.) new case record type for empowerment cases 2.) NOTES: a.) Who's going to handle these cases? Will a queue own them initially? b.)
1.) new case record type for empowerment cases 2.) NOTES: a.) Who's going to handle these cases? Will a queue own them initially? b.)
![Custom Links & Buttons in Salesforce Sometimes users just need a button! Raleigh Salesforce User Group Amber Neill Salesforce.com Administrator iContact.com [email_address] [email_address] http://www.twitter.com/amber9904](https://image.slidesharecdn.com/customlinksbuttonsinsalesforcecom-100222074740-phpapp02/85/Custom-Links-Buttons-In-Salesforce-Com-1-320.jpg)
![First things first... ,[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)