<< March 2017 | Home | May 2017 >>

Salesforce week 20-23

Wow I'm behind on these... I'll have to sum up the last 4 weeks and get better at doing these.

At the end of March I made Trailhead Ranger! I'm very happy that the ambitious goal of making Trailhead Ranger by the end of March was accomplished. On the Wednesday night in the bar of my second home (Radisson Hotel in Stockholm) I earned the last badges to bring me over the line. Great! I hurried over to my V2MOM to complete that measure on my FY18 V2MOM. Check! Next up is getting started on my Certified Developer I certification.

I also received emails about certification renewal. Oh well...

Last week was of course the terrorist attack in Stockholm :( The truck hit the building just 100m or so from one of the Salesforce offices. So sad and frustrating why people cannot just agree to disagree....

What else? I've been head down in work finishing of the first release at my customer I have been a part of and working on new existing stuff. I already had one big component deployed to production and on next Tuesday my next big contribution is being rolled into production and I'm really excited about it. Both are Salesforce Lightning components and they are pretty slick. Really shows what can be done. Once these are out I promise to record a video and post it. I also have loads of experiences and new stuff about Lightning development to share here on this blog.

On a more sad note my on-boarding buddy Rasmus got a new role inside Salesforce and will be switching teams. I'm really excited for him but I'm sad to see him leave our team and my current project. He's really a nice guy and a super competent architect. Glad he's still part of the Ohana though.

What did I learn

  • Lightning, Lightning, Lightning
  • More Lightning
  • Funky quirks about picklists from SOQL now that all picklists contains both an alias and a value
  • APEX performs really really well

Status after this week

Trailhead points: 85325
Trailhead badges: 100
Certifications: 5 (Salesforce Certified Administrator, Salesforce Certified Platform App Builder, Salesforce Certified Advanced Administrator, Salesforce Certified Sales Cloud Consultant, Salesforce Certified Service Cloud Consultant)

Tags :

Case in point - why we have API limits

This week the customer I'm working for went live with the next phase of their Salesforce rollout. The phase includes a Contact Sychronization feature where Salesforce contact objects are synchronized to users mobile devices using their Google Account. The contacts are flagged either in bulk or specifically using a Lightning Component on the Contact Page, has Salesforce1 integration to allow users to perform and manage sync on the go as well as a delegation feature to allow other users to manage their synchronization settings on their behalf. Think managing partners etc...

Anyway we went live on Monday morning and Tuesday morning the news hit. We had hit the API limit. The API limit is a hard upper limit on the number of API calls any customer may do towards Salesforce from external applications. There are a number of factors deciding the actual limit such as user count, license types etc. but in this case the limit was 500.000 calls in a 24 hour rolling period. We were at 555.593! Not good and and it was only 9am. Hmmm what could be wrong?

After looking into the matter we found out that the culprit was - you guessed it - the Contact Sync. The actual sync component that does the reads from Salesforce and writes to the Google Accounts of the Contact Sync feature was set to run every 10 seconds and not every 15 minutes as planned. At this rate the customer would hit an estimated 20.000.000 (20 million) API calls in a 24 hour window. Not good. A simple reconfiguration and we were back on track.

Talking to the friendly people at Salesforce Support we were even given an extra allowance of API calls for the day and the customer were back in business.

But case in point - this is exactly why there are (API) limits. If you hit the limits you are probably doing something you shouldn't. Well hopefully that's why you hit the limit.

Tags :