Skip to main content Salesforce and Tableau exam registrations are now closed through July 21st. Learn more about the new Salesforce certification experience coming soon.

Feed

Connect with fellow Trailblazers. Ask and answer questions to build your skills and network.

Hi Folks, 

 

We have a scenario where we need too refresh the CRMA dashboard as the data in salesforce record is updated, So is there any way we can trigger recipe from salesforce on record update. 

 

Also we open to new ideas or alternatives that we can use for this usecase. 

 

1 answer
  1. Today, 3:17 PM

    Triggering a recipe after updating a Salesforce record is technically feasable. But if the changes are happening more often, you will run into limits regarding the number of recipe runs per day. 

    Are you aware of the option to send direct queries (near-real time queries) against Salesforce objects? This is using SOQL, which has some limitations, but might fulfill your requirements to get near-realtime data displayed in a CRM Analytics dashboard.

0/9000

I am using the following statement: "{!URLFOR('/apex/echosign_dev1__AgreementTemplateProcess', null,  [masterId=Account.Id

,templateId='a02E0000004zfWmIAI'])}"   This keeps giving me Page does not exist enter a valid URL and try again.  Can anyone help me with this.  Thanks 

 

#Salesforce Developer

0/9000
2 answers
0/9000

Step not yet complete in Wise Otter Playground

We can't find the field 'Zone__c' on the Lead object i created but also showing error 

 

 

#Trailhead Challenges

2 answers
  1. Today, 3:12 PM

    Hi, @Vijay Kulal 

    This error indicates that the validation system cannot find a field with the API Name Zone__c on the Lead object.  

     

    Therefore, you need to follow these steps: 

    1. Open the Lead object via Object Manager, select Fields & Relationships from the left-hand menu, and check whether such a field exists and whether its API Name is indeed: Zone__c.

     

    If the field does not exist, you need to create it. If the API Name is different, you can delete this field and create a new one with the correct details. 

     

    2. If the API Name is correct but the error still occurs, check whether all necessary permissions are granted. To do this, click the field name, select Set Field-Level Security, and make sure the Visible checkbox is enabled. 

     

    For example,Hi, This error indicates that the validation system cannot find a field with the API Name Zone__c on the Lead object. Therefore, you need to follow these steps: 1.2.jpgSincerely, 

    Mykhailo Vdovychenko 

    Bringing Cloud Excellence with IBVCLOUD OÜ

0/9000
2 answers
  1. Today, 3:12 PM

    Hi, @Vijay Kulal

     

    This error indicates that the validation system cannot find a field with the API Name Zone__c on the Lead object.  

     

    Therefore, you need to follow these steps: 

    1. Open the Lead object via Object Manager, select Fields & Relationships from the left-hand menu, and check whether such a field exists and whether its API Name is indeed: Zone__c.

     

    If the field does not exist, you need to create it. If the API Name is different, you can delete this field and create a new one with the correct details. 

     

    2. If the API Name is correct but the error still occurs, check whether all necessary permissions are granted. To do this, click the field name, select Set Field-Level Security, and make sure the Visible checkbox is enabled. 

     

    For example,Hi, This error indicates that the validation system cannot find a field with the API Name Zone__c on the Lead object. Therefore, you need to follow these steps: 1.2.jpgSincerely, 

    Mykhailo Vdovychenko 

    Bringing Cloud Excellence with IBVCLOUD OÜ

0/9000

What is the intended purpose of the ContactProfile object and when should a custom field be added there instead of on the Account? It seems like ContactProfile has more private and permanent data that is unlikely to ever change, for example, Birthplace. I'm adding a custom field and on the one hand, it is personal information but on the other, it can change. Is there conventional wisdom yet on choosing one object over the other? Does ContactProfile have some special automations or analytic features?

3 answers
  1. Today, 3:11 PM

    I can imagine a use case that requires complex sharing of this data. Say, users can only see it for some contacts, but not all. FLS wouldn't work in that case, as a user with read access to the field would be able to see it on all contacts that have read access to it. But, as others have said, it does add a layer of complication that might not be worth it.

0/9000

Existing Formula 

ARR__c * 

CASE(Type, 

"New Logo", CASE( Sales_Person__c , 

"Sales Person 1", 0.00, 

"Sales Person 2", 0.00, 

"Sales Person 3", 0.10, 

"Sales Person 4", 0.10, 

"Sales Person 5", 0.10, 

"Sales Person 6", 0.10, 

"Sales Person 7", 0.10, 

0), 

"Renewal", CASE( Sales_Person__c , 

"Sales Person 1", 0.025, 

"Sales Person 2", 0.025, 

0), 

"Renewal+Upsell", CASE( Sales_Person__c , 

"Sales Person 1", 0.025, 

"Sales Person 2", 0.025, 

0), 

"Upsell", CASE( Sales_Person__c , 

"Sales Person 1", 0.05, 

"Sales Person 2", 0.05, 

"Sales Person 3", 0.05, 

0), 

0) 

 

Fields to consider 

ARR__c 

ARR_Upsell__c 

 

The logic needs to change as follows: 

 

on New Logo 

value = ARR__c * the pct for the Sales Person X 

  

on Renewal 

value = ARR__c * the pct for the Sales Person X 

  

on Renewal+Upsell 

value = ARR__c * the pct for the Sales Person X  + ARR_Upsell__c * the pct (could be diff) for the Sales Person X 

  

on Upsell 

value = ARR__c * the pct for the Sales Person 

 

#Reports & Dashboards  #Formulas

1 answer
  1. Today, 3:11 PM

    Hi @Matt Pinkston

     

    Please try using the below formula - 

    CASE(Type, "New Logo",  ARR__c  *   CASE(Sales_Person__c, 

    "Sales Person 1", 0.00, 

    "Sales Person 2", 0.00, 

    "Sales Person 3", 0.10, 

    "Sales Person 4", 0.10, 

    "Sales Person 5", 0.10, 

    "Sales Person 6", 0.10, 

    "Sales Person 7", 0.10, 

    ), 

     

        "Renewal", ARR__c *  CASE(Sales_Person__c, 

                "Sales Person 1", 0.025, 

                "Sales Person 2", 0.025, 

                0 

            ), 

     

        "Renewal+Upsell", ( ARR__c * CASE(Sales_Person__c, 

    "Sales Person 1", 0.025, 

    "Sales Person 2", 0.025, 

            ) +  ( ARR_Upsell__c * CASE(Sales_Person__c, 

                    "Sales Person 1", 0.05, 

                    "Sales Person 2", 0.05, 

                    "Sales Person 3", 0.05, 

                    0 

                ) 

            ), 

     

        "Upsell", ARR__c * CASE(Sales_Person__c, 

                "Sales Person 1", 0.05, 

                "Sales Person 2", 0.05, 

                "Sales Person 3", 0.05, 

                0 

            ),  

    0 ) 

     

0/9000
2 answers
0/9000

This might not be totally specific to mobile, but... currently accessing the standard login screen on mobile, with Android's Edge-to-edge (https://developer.android.com/design/ui/mobile/guides/layout-and-content/edge-to-edge

) enforced, means my top android bar (icons for battery, time, etc) all appear to disappear as they're white on white. 

 

With our custom mobile apps this isn't an issue for once you're "in" an app as we cater for this with CSS, but during login I don't think I have the power to alter this. 

 

I'm asking here as I would think that anyone going through the standard

login.salesforce.com

page (and forgotten password, etc) would have issues on Android Edge-to-edge enforced apps (which will be the default in the future). So in essence affecting anyone using the Mobile SDK, or mobile publisher (if not going via a community). 

 

Can anyone from the Salesforce team confirm that they're aware of Android's edge-to-edge, and that the needed changes (I think just CSS) will be in place on these standard pages? 

 

#Mobile #Android

0/9000