Feed

Hi @Ravikumar Chethi

  I created one permissions Sets  (Update Candidate Records) 

1. Under Object Permissions, enable the Read permission.
2. Under Field Permissions, enable the required field permissions.

Please Check

@Heiko Lindner

The Original Appointment was set for 09:00 AM - 10:00 AM and now I want to move this very appointment back by 30 Minutes to 09:30 AM - 10:30 AM.  

Unfortunately the Lightning Scheduler Component for flow does not offer me this specific slot. I think that this is the case because the original appointment time slot does overlap with the new one.  (09:30 - 10:00)  

I hope this clarifies it a bit.

Hello @真央 福田, you may try something like

AND( 
    lock_Proposer__c ,
    ISCHANGED( Proposer__c ),
    NOT( $Profile.Name = "System Administrator" ) 
)

Eric

Oh great, then the fact it's only a text field shouldn't matter. 

When you create a new field, select formula, with return type 'text' and click 'Next'. 

Make sure you're on the 'Advanced Formula' tab and click the 'Insert Field' button:

In the pop up box you will see all the fields on the Opportunity record including the 'lookup fields', which will have an arrow next to them. 

Scroll until you find the 'Primary Contact >' option and click it. You are then looking at all the fields on the Contact record linked via the 'Primary Contact' field on your Oppty. 

Find and select the email field. Hit Save.

That should then find and return the email address from the Contact record linked to each Oppty via the 'Primary Contact' field. 

Hope that helps!

@Cristiano Bruno Teles

thanks for the details. Means in your example, all three SAs have been scheduled on the same day, but the SA planned in the middle, has been done earlier then planned, right?  

Would it make sense to update the scheduled date of the SA2, if it's done earlier then planned and trigger the optimizer to update the current schedule for the resource.  

Maybe the optimizer triggers the planned times incl. travel time, if you trigger this one in just a case. I never had a use case like this. I would reschedule the appointment SA2, if this was done earlier then planned.

Hello @Abdelhakim Shrief have you tried adding a rule on  new SVMXC__Active__c 

state (fire it only when it has changed, and the new value is true) ?

AND( 
    SVMXC__Active__c = TRUE
    ISCHANGED( SVMXC__Active__c ),
    ISBLANK(Service_Contract_Key_Contacts__r.Key_Contact_Phone__c)
)

Eric

Same here, I think we need some more details about the process and current architecture. It should be possible, maybe you need a junction object to link contracts with opportunites or the other way around.

To help others that may run into this issue as well, neither Knowledge Base or File Upload based Data Library seems to be processed by Salesforce immediately. In conversation with Salesforce support I discovered that it can take 1-2 hours for File Upload to Data Library to be processed and indexed for use by Agentforce. In my own testing Knowledge Base is not immediately processed either by Salesforce though I am not certain exactly how long it takes. Some of my Knowledge Base was not parsed by Agentforce until 15-20 minutes at least after I have published them, others seems to take even longer.

Hi @Aditya Kiran Mishra

You can update the

apexCopyEditString activeMarketplace = String.join(marketplaceNamesList, ', ');

This will ensure all related Marketplace

names are combined into a single string with commas separating them. 

for (Marketplace__c mp : [SELECT Id, Name, Asset__c FROM Marketplace__c WHERE Asset__c IN :assetToAccountMap.keySet()]) { 

        Id accountId = assetToAccountMap.get(mp.Asset__c); 

        if (!accountToMarketplaceNames.containsKey(accountId)) { 

            accountToMarketplaceNames.put(accountId, new List<String>()); 

        } 

        accountToMarketplaceNames.get(accountId).add(

); 

for (Id accId : accountToMarketplaceNames.keySet()) { 

        Account acc = new Account(Id = accId); 

        acc.Active_Marketplace__c = String.join(accountToMarketplaceNames.get(accId), ', '); 

        accountsToUpdate.add(acc); 

    } 

    if (!accountsToUpdate.isEmpty()) { 

        update accountsToUpdate; 

    } 

Thanks, 

A. Gobinath

Hello @Catriona Cassidy you have around 20 possible values per bucket (see the considerations here : https://help.salesforce.com/s/articleView?id=000385482&type=1) 

An ID is not a good field to group by / to bucket. You should use relationships to maybe leverage a field from a parent / the lookup'ed record, to avoid an ID grouping. A formula field could be a possible way to operate that way. 

How to add a bucket column : 

https://help.salesforce.com/s/articleView?id=analytics.reports_bucketing_adding.htm&type=5

Eric