#Sales And Marketing18 人がディスカッション中

Hi Kim,

You can set this up using Custom Links on the Home Page Layout! Here is how to create those quick calendar links:

1. Get the Calendar URL

• Navigate to one sales rep’s calendar page.
• Copy the URL from your browser address bar. It usually looks like: /00U?cType=1&cal_id=USER_ID_HERE

2. Create the Custom Link

• Go to Setup > Customize > Home > Custom Links.
• Click New, give it a label (e.g., "John's Calendar"), and paste the URL.
• Set the Behavior to "Display in new window" or "Execute in new window" so it opens in a separate tab as you mentioned!

3. Add it to the Nav / Sidebar

• Go to Setup > Customize > Home > Home Page Components.
• Create or edit a Custom Component (type: Links), select your newly created link, and save.
• Finally, go to Home Page Layouts, edit your layout, and check the box to include your new Links component in the sidebar!

Good luck with the campaign kick-off on Monday!

Hi Madeleine,

Usually when this happens, the records actually did get created in Salesforce, but the connector just failed to write the new IDs back into your sheet!

A couple of things to check:

1. Try going to Salesforce and checking the "All Accounts" list view sorted by Created Date (sometimes they don't show up in Recently Viewed right away).
2. Make sure you mapped the Salesforce Id field to Column A in Excel during setup so it knows where to return the new IDs.
3. Double-check that you selected Insert and left the ID column completely blank before running it.

Hope this helps! Let us know if you're still stuck.

Hi Jake,

The error indicates that the ContactTrigger is failing during the BeforeInsert operation because a required Name field is missing. 

The important part of the error is:

This usually means the trigger or related Salesforce configuration is trying to create a record without populating a required Name field. It may not necessarily mean that Salesforce is missing a field from Outlook. 

Please check the pba.ContactTrigger code and any related automation to see where the required Name value is being populated. Also verify the Salesforce for Outlook field mappings and the affected Outlook contact. 

If you can provide the ContactTrigger code and the relevant field mappings, more specific guidance can be provided.

Hi Ryan,

The columns in the Task Reminder popup (Type, Subject, Reminder) are part of Salesforce's standard UI and aren't configurable through the Task page layout.

Unfortunately, you can't add the Account column to that popup using the standard setup options. 

A workaround would be to include the Account name in the Task Subject or use a custom Visualforce page/component for a more detailed task reminder view. 

The Account name being shown elsewhere on the reminder page doesn't make it available as an additional column in the popup.

Hi Orian,

A cross-object formula won't work for this because Lead Owner is a field that needs to be updated, not just calculated. 

Since the email activity is being created by iHance, an Apex trigger on Task would be a good option. When a Task is created:

1. Check whether Task.WhatId is a Lead.
2. Check whether the Lead is currently owned by a Queue.
3. If so, use Task.OwnerId to update the Lead's OwnerId.
4. Make sure the trigger is bulkified since iHance may create multiple activities at once.

You could also use Workflow/Process automation if the required Task and Lead fields are available, but Apex gives you more control over the queue check and owner update. 

If you can share how iHance populates the Task fields, especially OwnerId and WhoId/WhatId, the exact trigger logic can be determined.

Hi Demps,

The message about the “inforce connector” suggests that the Request Update feature is using a third-party LinkedIn integration rather than a standard Salesforce feature. The “solution provider” would therefore be the vendor that supplied that connector/integration. 

Since this is from 2012, the LinkedIn integration/API may no longer be supported, which would explain why the login/authorization step is failing. The Salesforce Community post itself does not identify the provider or provide a current fix. 

I would check Setup → Installed Packages and Connected Apps for the Inforce/LinkedIn integration and identify the package/vendor. If the package is no longer supported, the Request Update feature would need to be replaced or updated with a supported LinkedIn integration. 

If you can provide the Inforce package name/version o

Hi Jeremy,

If you're using the LinkedIn API, Salesforce reporting won't automatically query LinkedIn and join the current LinkedIn values to your Salesforce Contact record. 

A typical approach would be to store the LinkedIn Unique ID on the Contact, then have an integration periodically call LinkedIn's API and update separate Salesforce fields such as:

• LinkedIn Current Name
• LinkedIn Current Company
• LinkedIn Current Job Title
• Last LinkedIn Check Date

You can then report on both your Salesforce-stored values and the latest values retrieved from LinkedIn in the same report. 

Whether LinkedIn for Salesforce provides those fields or change tracking depends on the specific integration/version you're using. If you share which LinkedIn package/API you're using, I can be more specific. 

For tracking job/company changes, storing a dated history of the retrieved values is also useful rather than simply overwriting the previous value.

Hi Nancy, 

If the Campaign Members show “Unsent” while the others show “Sent,” you can use the Campaign Member status to identify those records.

I'd create a Campaign Member report filtered by:

• Campaign = your campaign
• Member Status = Unsent

You can then review those Leads and use that list for your follow-up email.

If the Mass Email wizard doesn't allow filtering by Campaign Member Status, you may need to create a separate Campaign/list view containing only those Leads and send the mass email from that list.

Hi Greg,

The “Restrict Visibility” option for list views isn't controlled by a profile permission that you can simply enable for Standard Users. 

In Professional Edition, the ability to create/share public list views is limited by the user's permissions and edition capabilities. Standard Users may only be able to create views for themselves, while administrators can create views visible to other users. 

If your users need to share Lead views with colleagues, check the user's profile permissions and the specific Professional Edition limitations for your org. If the option is still missing after confirming the permissions, Salesforce Support can verify whether it's an edition limitation or an org-specific configuration issue.

Hi Jason,

For Content Delivery, the generated link is an external Salesforce URL, so whether it gets blocked depends on the recipient's email/security filtering. There isn't a guarantee that every customer's spam filter will allow it. I'd recommend testing with the mail systems your customers commonly use before relying on it for quote packages. 

For your second question, the standard Send an Email → Attach File functionality doesn't provide a direct browse option into CRM Content libraries in the way you're describing. Content Delivery is intended for sharing library content externally. 

If you need to send the actual file as an email attachment, you may need to download the file and attach it, or use a custom/integration-based solution that retrieves the Content file and attaches it to the email.