Skip to main content

#Automation29 discussing

My org recently switched to Lightning - in Classic the subject field for tasks was predictive based on what a user has used in the past. In Lightning this does not work - however, the user can switch back to classic and it will still work. After initial research the only thing I can find is that clearing browser cache ~might~ work. I have seen several places where people are asking about this but there are no definitive answers. Have others ran into this? If so, how have you fixed it?

1 answer
  1. Aug 24, 6:40 AM

     You may want to check the Lightning Task settings and browser cache first. Also try testing with another browser or user profile to rule out a local issue. If it works correctly in Classic but not Lightning, it may be a Lightning-specific limitation or bug rather than a cache problem. 

0/9000

Versions of flows in production that were not active were being executed even though they were not active. I deleted the Not-Active versions of flows and problem was resolved.  Anyone ever experience anything like this?

 

For clarity - this was happening both in Debug with option to use latest versions of flows Unchecked and also happening running the live versions of the flows in production. 

18 answers
  1. Andrew Russo (BACA Systems) Forum Ambassador
    Jul 11, 2022, 3:19 PM
0/9000

It would be good if Trailhead Trackers capabilities could

Include available points per badge

How many points a user has earned for each badge

If you complete a badge and it is the revised and extra content is added how you can be made aware

Also could certification and quest data be added so they can be assigned to users without manually creating a badge and then this data also pulled from a user’s trailhead profile

#Automation #Trailhead #Integration
1 answer
  1. Aug 20, 8:54 PM

    Hi Dan - the app is Trail Tracker (Salesforce Labs, free on AppExchange). It syncs each user's earned + in-progress badges, points and trailmixes daily via an API integration user, lets you ASSIGN badges/trailmixes, and ships with pre-built reports and dashboards. So 'how many badges/points a user earned' and assigning learning are covered out of the box. 

     

    The specific things you listed are NOT native, though: 

     

    - Available points per badge (earned vs available): it syncs what's earned, not a catalogue of available points - you'd maintain that reference yourself. 

     

    - Alerts when a completed badge is revised or gets new content: no mechanism. Trailhead doesn't surface 'this badge changed' through the sync. 

     

    - Certifications: not synced. Certs aren't badges (they live in a separate system), so it won't pull them - track those manually or via a separate integration. 

     

    - Quests: not a standard synced object either (quests are temporary badge campaigns). 

     

    The upside: Trail Tracker is a Labs app, so you get the objects and code - you can extend it (custom fields for available points, a flow to flag changes, a custom object for certs) rather than build from scratch. Out of the box, though, it's badge/points/trailmix tracking + assignment, not the full picture you're after. 

     

    If this helps, please mark it as the Best Answer so it points the next person the right way - 🙂

0/9000

I’m working on a Salesforce org with several Flows, Apex triggers, and scheduled automations. As the amount of data grows, some processes are taking longer to complete and a few users are seeing delays during record updates. I’d like to understand which areas I should check first, such as Flow design, Apex execution, SOQL queries, or automation order. What tools or best practices do you recommend for finding the main performance bottleneck? 

 

#Salesforce Developer  #Automation

1 answer
  1. Aug 20, 3:21 PM

    Hi Matteo - great instinct to measure before optimizing. The order I would work in: 

     

    1) Find the bottleneck, do not guess. Set a trace on an affected user, reproduce a slow record update, and open the debug log in Developer Console - the log timeline shows time spent per operation (SOQL, DML, each trigger, each Flow). Filter for SOQL and DML events to spot the heavy hitters. If you have Event Monitoring, its performance event logs and dashboards surface the slowest transactions org-wide, not just one repro. 

     

    2) The number-one reason automation 'gets slower as data grows' is non-selective SOQL - queries whose filters are not selective do full table scans that degrade with volume. Run each query through the Query Plan tool (Developer Console, Query Editor, Query Plan): aim for filters on indexed fields (Id, Name, lookups, External Id, or a custom index), and avoid not-equals, NOT, and leading-wildcard LIKE. Usually the single biggest win. 

     

    3) Then the usual suspects, highest ROI first: 

    - SOQL or DML inside loops (in Apex OR a Flow 'for each') - bulkify: query once into a Map, do DML once on a collection. 

    - Too many automations firing on save - Flows, triggers, and any legacy Workflow/Process Builder all run on every update and can even re-trigger each other. Consolidate to one trigger per object (handler pattern) and trim record-triggered flows. 

    - Same-record field updates? Use a before-save (fast field update) flow - dramatically faster than after-save plus a record update. 

    - Move non-urgent work async - Flow's Run Asynchronously path, or Apex Queueable/Batch - so the user's save returns immediately. 

    - For scheduled/batch jobs on big objects, tune batch size and query selectivity. 

     

    Rule of thumb: measure with the debug log, fix SOQL selectivity first, then bulkification, then reduce and reorder the automations that run on save. 

     

    If this helps, please mark it as the Best Answer so it helps the next person - thanks :)

0/9000

Hi everyone — reaching out to this community as I explore my next role.

I’m a CBAP-certified Business Analyst with 20+ years of experience across federal government, FinTech, and SaaS, and I also hold Salesforce Business Analyst and SAFe Agile certifications. My background includes Salesforce flows and SOQL, data mapping, UAT leadership, and compliance documentation, with growing hands-on experience in AI and automation tooling.

I’m open to Senior BA, Product Analyst, BA/PM Hybrid, and Product Owner roles. If you know of anything open, or are hiring, I’d love to connect — happy to share my background in more detail.

Thanks for reading, and good luck with your own searches too.

#Trailhead #New Releases #Nonprofit #Automation
1 comment
0/9000

Hi Salesforce community,

 

Basic formula request here! Looking to automate the Due Date of a newly created Task to be 3 Business Days from Today. Any takers?

 

Thanks!

 

Tim

 

#Sales Cloud #Automation #Tasks

5 answers
  1. Aug 13, 2021, 5:00 PM

    Can you try this

     

    IF(MOD(TODAY() - DATE(1900, 1, 6), 7) > 3, TODAY()+5, (IF(MOD(TODAY() - DATE(1900, 1, 6), 7) = 0, TODAY()+4, TODAY()+3)))

     

    1900, 1, 6 was Saturday so in case you also create a task on Saturday then still the above formula will work bcoz then it will add 4 days to that 

     when Today is Monday, Tuesday then it will add 3 days, for Wednesday, Thursday, Friday it will add 5 days

     

    Hope this helps,

0/9000

Hi everyone — reaching out to this community as I explore my next role.

I’m a CBAP-certified Business Analyst with 20+ years of experience across federal government, FinTech, and SaaS, and I also hold Salesforce Business Analyst and SAFe Agile certifications. My background includes Salesforce flows and SOQL, data mapping, UAT leadership, and compliance documentation, with growing hands-on experience in AI and automation tooling.

I’m open to Senior BA, Product Analyst, BA/PM Hybrid, and Product Owner roles. If you know of anything open, or are hiring, I’d love to connect — happy to share my background in more detail.

Thanks for reading, and good luck with your own searches too.

#Integration #Trailhead #Analytics #Automation
1 comment
0/9000

 New in 360 InstantDocs: Excel File Generation for Salesforce

 

 

We're excited to share a new enhancement in

360 InstantDocs

on Salesforce AppExchange! 

 

With our latest release, you can now generate Excel (.xlsx) files directly from Salesforce—making it easier to automate spreadsheet creation without leaving your Salesforce environment. 

 

You can now generate formatted Excel (.xlsx) files directly from Salesforce and automate the process using Flow or Apex, making it easier to create reports, invoices, and other business documents.

 

We'd love to hear how you would use Excel generation in your Salesforce workflows. Feedback and suggestions are always welcome. 

 

#AppExchange  #Document Generation  #Automation

1 comment
  1. Aug 7, 9:48 AM

    Great update! Excel is still a common format for many business teams, so having this capability directly in Salesforce will be valuable for a lot of use cases. 

0/9000

I paused the automation, removed the wrong list (140 people), and added the correct list (36 people) back to the trigger. It now says people from both lists are in the automation (176 people). According to Salesforce's Engagement Studio FAQ and Agentforce, removing the old list and replacing it with the new list will also remove anyone on that old list from the flow. It says "anyone who was only on the wrong list will automatically exit the program immediately and will not receive any further emails". But it doesn't seem like those people from the first list were removed. Please help!  

1 answer
  1. Aug 6, 11:21 AM

    Hi @Clix Marketing Removing the incorrect list from the Engagement Studio trigger prevents those prospects from moving further only if that list was their only entry source. The participant count may not update immediately, and prospects who have already entered the program can still appear until Salesforce refreshes the data. Check the Prospects tab in the program to confirm whether the incorrect prospects are marked as removed or inactive. If they are still active, you can remove them manually or use a suppression/dynamic list to stop them from receiving additional emails. If the count never updates after some time, it may be worth contacting Salesforce Support, as this can occasionally be a sync or refresh issue.

0/9000

We have a client who is looking to run a number of marketing campaigns across LinkedIn, Instagram and Facebook. 

 

When someone signs up to their newsletter via one of the ads, they want the lead to be created in Salesforce, but they also want to be able to identify which specific ad or campaign the lead originated from. 

 

Our current thinking is that each ad would direct users to a web form on the client's website, which would then submit the information into Salesforce using Web-to-Lead. However, we're not 100% sure of the best way to track which ad the submission came from and pass that information into Salesforce.

Could someone advise on the best approach? Alternatively, if there's a better way of achieving this with little to no additional cost, we'd really appreciate any recommendations.

 

Thanks!  

 

 

#Web-to-lead  #Webform Values  #NPSP  #Leads  #UTM Parameters  #Automation

1 answer
  1. Jul 28, 11:57 PM

    Hi Philippa, a way to tell which ad a lead came from is UTM parameters captured via hidden fields on your Web-to-Lead form, plus a hidden Campaign Id field to auto link leads to a specific Campaign. This should be of no additional cost and is low complexity.

0/9000