Skip to main content

#Summer24Feedback0 debatiendo

[▶️]🔴🔥🎬 How to Only Update Salesforce Records Using External IDs in REST API

 

Before Summer 24 Release i.e. before API version 61, when you use the HTTP Patch call to do some update on record, Salesforce performs the upsert operation i.e. if the record found with matching external id, api call is going to update the matching record, but if there is no matching record with the external id, then api call is going to create the new record with the details provided in the HTTP call request body. So it is basically an upsert operation.

 

But after Summer 24 release i.e. API version 61, Salesforce is introducing a parameter which you can pass in the API call to make sure it will only do the update to the existing record and if the existing record not found, it is not going to create a new record. The process will stop there.

 

So in this blog post and youtube video, I am going to explain this powerful enhancement. Please provide your feedback what do you think about this new powerful feature.

 

🎬 https://youtu.be/5ci3QmD8F2Y

đź“’ https://sudipta-deb.in/2024/07/how-to-only-update-salesforce-records-using-external-ids-in-rest-api.html

 

[▶️]🔴🔥🎬 How to Only Update Salesforce Records Using External IDs in REST API Before Summer 24 Release i.e.

@The Blog Group @* Release Readiness Trailblazers *

 

#Summer24  #Summer24Feedback  #API  #RestAPI

0/9000

Since the summer '24 update we are having issues with the dashboard graphs not sorting correctly.

We can update, save, and it will be correct. But as soon as we refresh, it reverts back.

Is any fix available, or is this just an issue with Summer '24?

 

Correct:Dashboard Graph Issue

Wrong:Wrong Sorting Wrong.png

 

#Reports & Dashboards  #Summer24  #Summer24Feedback

1 respuesta
0/9000

Hi,

After Summer '24, we've encountered issues related to 'INSUFFICIENT ACCESS - user does not have a verified email address' from users when they try to send email to contacts from Salesforce. We discovered that users can log in via SSO to Salesforce even if their emails are not verified until Spring '24.

Starting Summer '24 users are unable to send emails unless their email addresses are verified 

While this information was included in the Winter '24 release notes, Salesforce should have provided some indications in the latest release to keep informed and alert about this major change. 

INSUFFCIENT ACCESS - user does not have verified email address

 Can I please check how to identify unverified users quickly and send instructions to those who haven't verified their email addresses in Salesforce.

With large number of users what will be the best process. Please share some knowledge.

Thanks

6 respuestas
  1. 18 jun 2024, 14:58

    We ran into this same insufficient access error too and found that this checkbox had been unselected during release update.  It's found in Setup>Deliverability.  Once we selected it, we were back in business.We ran into this same insufficient access error too and found that this checkbox had been unselected during release update. It's found in Setup>Deliverability.

0/9000