Hi!
Quick question: is DLRS calling any Heroku or AWS based application?
Thanks in adavance!
Hi!
Quick question: is DLRS calling any Heroku or AWS based application?
Thanks in adavance!
I wrote one validation rule related to stopping the update status of the activity, but when I am trying it directly on the lead page, it's not showing me an error, but earlier it was showing error. I also tried from another org its working fine for that org
FYI - Error is perfectly working on Record Page
Is there any new release related to activity
Attching Screenshot for Ref
#Trailhead Challenges #New Releases #Salesforce Developer #Flows #Flow #Validation Rule #TrailblazerCommunity #Trailhead Superbadges #Trailhead Developer Org
sure
AND(
TEXT(Status) <> TEXT(status__c),
TEXT(Follow_Up__c) <> "Yes"
)
I also tried with the trigger just to cross-verify ,but results are same its showing on record page or from any other source from where we updating the status ,just for this related view its not showing
Hello,
I need to figure out the best option to make the opportunity field 'Type' required. At the moment, my client's org doesn't create opportunities from lead conversion but might in the future so I want to bear this in mind.
I'm slightly confused because the opportunity page has dynamic forms set up.
I thought that the required field on the page layout (outside universally required fields) wouldn't have any impact on the Lightning Record page but, when I made the field 'Type' required on the Opportunity Page Layout, then created a new opportunity, saved it and then tried to move the opportunity to another stage, the field requirement message appeared "
You encountered some errors when trying to save this record
These required fields must be completed: Type".
Why did the error message appear when I changed Stage but not when I created the opportunity or updated other fields on the opportunity record?
Any rational explanation I'm missing?
What solution would you advise for force the Type field? validation rule? Lightning record page settings?
Thanks.
When you made the Type field required on the page layout, it does not enforce it on record creation via Dynamic Forms unless the field is on the layout and visible.
When you changed the Stage, this triggered a record update via a standard process which enforce the Page Layout Rule. Even though the dynamic forms are used for UI, server side logic honors it
Couple of options may seem valid
Create a validation rule of make the type field required and visible in dynamic forms
Hi everyone,
I’ve sent two emails to Salesforce requesting a discount for the Salesforce Administrator Certification, but unfortunately I haven’t received any response yet.
I made the requests through the official channels, and it’s been several days with no update. I would really appreciate any help or advice on how to move forward or if there’s another way to access the discount.
Thanks in advance!
Best regards,
Carla Elgart
i am implementing the smart list inside a screen flow. I get the data from an apexdatasource. i want to pass to the getPage function some parameters (2 collections/string arrays) which are calculated in the flow (prior to the screen). how can i pass them? thanks!
Hi @Ehud Lahav
,
There is no standard way to pass flow data to getPage. You could consider storing your data in the Session cache so that you can read it in getPage
https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_platform_cache_session_examples.htmHi all, please help! I stuck on conditions for my flow. I am creating fast fields update flow, on the case object. I am creating a formula but it is throwing an error: AND(
CONTAINS({!$Record.Case_Owner_Role__c}, "Second Line"),
{!$Record.CaseRecordType__c} = "Customer_Support",
TEXT({!$Record.Status}) <> "Closed"
)
Error: Error in referenced formula $Record.Case_Owner_Role__c, Field Owner:
User.Iddoes not exist. Check spelling.
Field Case_Owner_Role__c is a formula field: Data Type Formula
IF(ISBLANK( Owner:
User.Id ), Owner:Queue.QueueName, Owner:User.UserRole.Name)
What I want to do is to reference it. I added CONTAINS as user role can be Second Line or Second Line Manager. Any ideas? Thank you
Instead of referencing the Formula field in your Flow, I would try using the Formula itself (re-written an Flow Formula Syntax)
Hi all, please help! I stuck on conditions for my flow. I am creating fast fields update flow, on the case object. I am creating a formula but it is throwing an error: AND(
CONTAINS({!$Record.Case_Owner_Role__c}, "Second Line"),
{!$Record.CaseRecordType__c} = "Customer_Support",
TEXT({!$Record.Status}) <> "Closed"
)
Error: Error in referenced formula $Record.Case_Owner_Role__c, Field Owner:
User.Iddoes not exist. Check spelling.
Field Case_Owner_Role__c is a formula field: Data Type Formula
IF(ISBLANK( Owner:
User.Id ), Owner:Queue.QueueName, Owner:User.UserRole.Name)
What I want to do is to reference it. I added CONTAINS as user role can be Second Line or Second Line Manager. Any ideas? Thank you
Instead of referencing the Formula field in your Flow, I would try using the Formula itself (re-written an Flow Formula Syntax)
Hi all, please help! I stuck on conditions for my flow. I am creating fast fields update flow, on the case object. I am creating a formula but it is throwing an error: AND(
CONTAINS({!$Record.Case_Owner_Role__c}, "Second Line"),
{!$Record.CaseRecordType__c} = "Customer_Support",
TEXT({!$Record.Status}) <> "Closed"
)
Error: Error in referenced formula $Record.Case_Owner_Role__c, Field Owner:
User.Iddoes not exist. Check spelling.
Field Case_Owner_Role__c is a formula field: Data Type Formula
IF(ISBLANK( Owner:
User.Id ), Owner:Queue.QueueName, Owner:User.UserRole.Name)
What I want to do is to reference it. I added CONTAINS as user role can be Second Line or Second Line Manager. Any ideas? Thank you
Instead of referencing the Formula field in your Flow, I would try using the Formula itself (re-written an Flow Formula Syntax)
Hey all! I’m a Salesforce Admin at a SaaS company, and we’re trying to make a decision on how to handle returning customers who were previously churned. It doesn’t happen super often, but we’ve had a few customers come back recently and it’s raising some questions.
The main issue, is we integrate with other solutions (Intacct/Adaptive Planning) for financial and forecasting. A new Intacct ID is required when they return, which makes it cleaner to create a brand new Account in Salesforce. On the other hand, I don’t love duplicating Accounts because we lose historical context in the CRM, and it can get messy for our Sales, CS, and Support teams.
I’m wondering how others handle this — reopen or create new?
Here’s the options we're considering:
Option 1: Reopen the old Account
Option 2: Create a new Account
Possible Hybrid Approach:
Curious to hear how others handle this in integrated orgs. If you’ve dealt with this before, what worked for you? Any suggestions or best practices to share with this use case? Thanks in advance!
We are in the middle of having this discussion internally as well. I like the hybrid idea since there are other departments that are pushing for creating a new account. I'm curious to see what route you take!
Hi,
I am working on Superbadge of Agentforce Innovator -Agentforce for Service Superbadge Unit. While trying to finish 2nd challenge under this "
Create the Booking Management Topic".I am unable to find the Agent Actions under setup.
Can anyone please help me with this? Thanks in advance!
#Trailhead Challenges