Tips and Takeaways From Getting the Apex Specialist Superbadge

Quick tips for the Apex Specialist Superbadge. I’ve started the new certification path for the Platform Developer II as I already passed the multiple choice question a long time ago but it was ridiculously hard getting a slot on the programming assignment. With this new format, I would need to complete these four superbadges.

So, 1 out 4 completed. I got the Apex Specialist Superbadge nailed.

For the Apex Specialist superbadge. There are a total of 6 mini challenges you need to complete. Requirements are straightforward. If you been developing on the platform for some time, the challenge should be a breeze. It took me 6 hours though to complete the challenge.

Takeaways from the challenge

  1. There are many options for building the solution. Just stick with where you are most familiar with.
  2. Use maps for more efficient querying and to bulkify your triggers
  3. I thought I already know all my JSON stuffs until I tried to manually parse a JSON string. Get familiar with using the JSON class methods. Check my post on Demystifiyng JSON parsing in Apex.
  4. Given another chance since the requirements are not that complicated this would’ve been a good practice to have tried test-driven development.

If you need help completing the challenge hit the comments below and I’ll be glad to help. Good luck on getting that superbadge.

3 thoughts on “Tips and Takeaways From Getting the Apex Specialist Superbadge

  1. not able to complete sir. error is
    Challenge Not yet complete… here’s what’s wrong:
    There was an unexpected error in your org which is preventing this assessment check from completing: System.DmlException: Insert failed. First exception on row 0; first error: FIELD_CUSTOM_VALIDATION_EXCEPTION, Validation Formula “RecurringChargeTypeMustHaveBillingType” Invalid (Field 00N6F00000HyvBc is inaccessible. Please review all fields referenced by the formula. Context: common.config.entity.ValidationFormulaContext): []

Leave a Reply

Your email address will not be published. Required fields are marked *