Feed

If you're in Chrome, this may fix it. For some reason there seem to be some cookies or other storage saved for Salesforce today that's causing this issue, at least as far as I can tell trying to troubleshoot it. When I cleared all data saved for Salesforce per below, that worked. Please note - I don't know what content/data you may have saved for Salesforce, that may affect you; I didn't have anything meaningful. The only impact for me aside from this fix is I had to log back into Salesforce sessions that had been open. 

• Go to the following link in Chrome: chrome://settings/content/all
• On that page, search for “force” and then clear everything saved for both Salesforce.com and Force.com, using the trash can icon
• Once that’s finished, close Chrome, and re-launch it
• Now, click the Salesforce chrome extension again to launch it, and log into Salesforce again.

@TAKAUMI KIYAMA

さん 

追加情報です 

2026年12月15日（火）13:00-18:00 

認定Platformアドミニストレーターの無料ウェビナーがございます 

またSalesforce 認定資格試験: 受験料 50％オフキャンペーン（Certification Days）　も開催中ですのでご共有します 

Hi @Rosanne Lau

Please check this article.  

Hi @Troy Runge

You can do this right in reports with cross filters, no export needed. This assumes you track the event with Campaigns: 

1. Create a Contacts report.
2. Add a cross filter: Contacts WITH Campaign Members, with a sub-filter for this year’s event campaign and the RSVP status.
3. Add a second cross filter: Contacts WITHOUT Campaign Members, with a sub-filter for past years’ event campaigns and Status = Attended.

What’s left is everyone who RSVPed this year and never attended before, whether they’re new or have been in your database for years. 

Tip: if each year is a separate campaign, put them under a parent campaign or give them a common Campaign Type. That makes the “past events” filter easy to maintain. 

For something longer term, add a rollup field on Contact like “Annual Event Attendance Count” (NPSP Customizable Rollups or a Flow). Then it’s just a filter of count = 0.

When custom service appointment statuses are mapped to standard states like "Scheduled" or "Dispatched", the Gantt chart and dispatcher console rely on specific status category assignments under the hood to determine which items are eligible for drag and drop scheduling. If the custom status metadata or status transition mapping is missing the proper category alignment, the console treats the appointment as locked or unschedulable via direct drag and drop, even though explicit button actions like clicking "Schedule" execute standard backend logic that bypasses UI drag constraints. To resolve this, verify your custom status mappings in Field Service Settings under Status Mapping to ensure every custom status is correctly tied to its corresponding dispatcher state category. Additionally, check that your dispatcher profile or permission set has the correct service territory and scheduling policy assignments, and ensure that the Gantt chart layer filters aren't actively hiding or locking the specific status category from interactive drag-and-drop manipulation.

Hi @Elina William

Matt’s answer is spot on. A few things that helped me reason through those scenario questions: 

• Routing: the agent picks a topic first, based on the topic’s classification description and scope, and then picks an action based on the action’s instructions and its input and output descriptions. Most “wrong action” scenarios come down to vague descriptions.
• Overlapping topics: the fix is usually sharper descriptions and scope, not more instructions. If two topics sound alike, the agent will guess.
• Standard vs custom: use standard actions when they fit. Go custom with Flow for business logic, Apex for complex logic, and Prompt Template for generated content.
• Failures: build fault paths into your flows and return a clear output message, so the agent can respond gracefully instead of stalling.
• Instructions: keep them for guardrails and sequencing (“always confirm the order number before cancelling”), not for business logic.

Hi @Derek Johnson

There’s no escape character for commas in list view filters. Quotes won’t work, because the comma is always treated as a separator. 

On top of Matt’s suggestions, a few options I’ve used: 

• Use “contains” with a unique part of the name, for example “Salesforce, Inc” becomes “Salesforce”. Check it doesn’t pull in similar names.
• If the list is a fixed set of accounts, add a checkbox or picklist field (for example “Key Account”) and filter on that instead of names. It’s cleaner and easier to maintain.
• For a formula field, use SUBSTITUTE(Name, “,”, “”) and filter on that.