Feed

Hey folks, 

Hoping y'all can help me come up with some alternatives here. 

It appears when creating a service schedule, adding service participants, then going into one of thew auto-created sessions, the attendance tracker is set to 'Present' by default for each Participant. Our client wants this set to 'None', so that the user can manually set the attendance for each participant. Unfortunately, this is all managed package, so we cannot reset or clear out the default. Our only alternative at the moment is replacing the attendance tracker with a custom component, identical to the original, that gives us more control over the individual fields. Has anybody else encountered this issue? Any creative solutions? 

Thanks, 

Rubin

Hi Everyone,  

First time poster and hopefully this is an easy one. would anyone be able to help me with this error please. 

Error Type: Scheduled Apex Error 

Error Date: 2025-06-24 23:57:57 

Message: "There are Scheduled Jobs owned by an inactive User. Review your Scheduled Jobs and ensure the owner of each one is an active User."

 am stuck on w rite Positive Tests and getting a error and trying to fix it 

Challenge not yet complete in Wise Koala Playground 

We can’t find the “AccountWrapperTests” class.  

I have an agent that returns a list of date/times for a user to select for creating an event record. The agent correctly retrieves the open time slots and renders a list of options with radio buttons, but does not render text of the option next to the button so I have no idea what option is what. How can this be resolved?  

#Agentforce

Hi, everyone! I am using NPSP and have an Opportunity Flow with several Decision Outcomes that updates a picklist field on the Opportunity (that triggers 1 minute after the Opportunity: Last Modified Date is updated). I keep receiving the following email error re: the Account record:  

The flow tried to update these records: null. This error occurred: UNABLE_TO_LOCK_ROW: unable to obtain exclusive access to this record or 1 records: <Account Id>. 

I've checked for other conflicting Opportunity or Account Flows but cannot figure out where the conflict is happening. :( Any help is much appreciated -- thank you!  

cc: @Dar Veverka @Judi Sohn @Nonprofit Success Pack @Nonprofit Ask Me Anything (Global) @Nonprofit Hub

#NPSP  #Flow  #Flows  #Salesforce Admin  #Nonprofit Success Pack 

We are looking to use either Verint or Calabrio as our Workforce Management System. We have to integrate it with Salesforce Service Cloud as well. Which one is preferred option. Have anyone implemented any of them and see any props or cons 

Customize a Salesforce Object (module) 

 Create Validation Rules (step) 

 Sir ,I completed all steps but i was getting this error message after clicking verify step to earn 100 [ error message -  Step not yet complete in My Trailhead Playground 1

An unexpected error occurred while inserting Opportunity records and we couldn't check your work. Make sure Opportunity records can be inserted in this org, and click "Check Challenge" again. If this continues, contact the Trailhead Help team. ] 

Step not yet complete in Data Cloud and Einstein AI

We check your work in the active version of the flow. In the 'Create Check-in Guest Event' flow, we found your most recent changes in a version that is not active. Activate the version you want us to check, then click Check Challenge again. 

I tried with both the versions which I have, please help 

Hi there, 

  I had a call with support today that made me realize I don't think there is a standard use case for this but would love to hear what the community thinks or has come up with to address this before.   We have restricted default sharing rules to private on Accounts and related records so that only the direct account owner can see the Account and it's related child records.  This was meant to protect accounts from reps trying to call in or scrape lists if they don't have a direct need for the details. 

  What I'm being asked to do now is to give all reps visibility to all accounts, but ONLY to a few base fields for the basic use case of identifying that an account indeed already exists, who owns it, and have visibility to the basic fields necessary to confirm a duplicate.  Account Name, Account Owner, Website, Phone, Address.  That's about it. 

   I thought about sharing rules, permissions, or page layouts but I don't believe any of these will work based on account ownership being dynamic.  My next thought is perhaps putting all of the relevant fields we don't want globally visible into a field section that is filtered based on account ownership, but I'm not clear how I would do that as the visibility filter only provides a static value entry.   

   If anyone has any thoughts or links to relevant solutions out there already I would be super appreciative.  I think the dynamic section is the best method I have so far, but still not clear how to get it completed. 

Thank you!