Skip to main content

Advanced Billing Specialist Superbadge - 1 & 2


What could possibly go wrong?

After (finally) fishing in the Billing Specialist superbadge, Trailhead Baby decided to jump right back in with the Advanced Billing Specialist superbadge! This time, I decided that it would be fun to try to trigger every possible error message.  Why?  Why not!  

Sometimes, the simplest approach to a superbadge is to start each step with a button click:
Why? Usually this approach will help you get started in the step, even before you have completed any of the needed actions!  If you run into a new error message that I did not post, please let me know. Trailhead Baby is trying to trigger all of the error messages for this superbadge- just for fun. 







Solution: Check the custom setting's "default" value.  It should be 18 digits starting with "a1p" that you copied/pasted from somewhere else.  Hint: Every record has a 18 digit value that makes the individual record unique. 


Hint: There are two places with "legal entity" in Salesforce after you create the custom setting.... They are easy to mix up! One is referenced by the other. 


If you need to delete a custom setting, ensure that it is fully deleted! This might me deacitvating/reactivating the process builder...especially if you see something like this: 


The record type was not correct! Remember- There are several options for legal entity. (Thank you Trailhead for making it a little confusing!) 

Still holding on? Ready for step 2?



When you read the instructions and have no idea what a 'finance book' could be, the simplest way to get help is to click "check challenge."  Ahhh apparently there is an object called 'finance book' and I need a finance book record, a period of some sort, and an active record.  Helpful!


Trailhead Baby only has one hint for step 2.  If you see this message (below), STOP!  Reevaluate and read this article before you do anything else:

"When you create a finance book, Salesforce Billing lets you automate the creation of monthly finance periods for each month within the finance book’s date range. You can also manually create individual finance periods. However, manually created finance periods must still run from the first to the last of a month."


Comments

  1. I am getting an error that you didn't record for the first challenge. Not sure why though, since I do have the custom setting created

    Challenge Not yet complete... here's what's wrong:
    We couldn’t find a Custom Setting named LegalEntity (LegalEntity__c). Please ensure that the custom setting was created according to the requirements.

    ReplyDelete
  2. Dear Trailhead Baby. Please help me before I pull out every hair on my head. I am working on this advanced badge and I keep getting the null error in challenge 2. I have the correct custom setting and I am pretty sure I have the correct ID in there. But my flow is kaput. At least that is where I believe the error is coming from. Here is my flow update element:
    All conditions met using the order product record that triggered the flow.
    blng__LegalEntity__c is null value of true
    blng__legalentity__c is $Setup.LegalEntity__c.LegalEntityID__c

    ReplyDelete

Post a Comment

Popular posts from this blog

Process Automation Specialist Superbadge - 5

A project with Daddy: My favorite daily process! Making dinner for Mom! Tonight's challenge involves the creation of two processes.   Processes.  Have you guessed the theme of the photos that go along with the Trailhead - Process Automation Specialist Superbadge series?They are a few of my favorite day to day processes!  You, my amazing reader, get more than tips for a Salesforce Superbadge.  You also get personal insight into the life of a Trailhead Baby!  I hope that you feel inspired. Process Builder sketch Last night, I drew a rough sketch of my process: Was it pretty?  No. Did it help?  Yes! The sketch allowed me to organize all of the instructions into a reasonable order before I started clicking.  It also removed the approval steps from Process Builder and highlighted (with *'s) the prerequisite items to building my process. * Email Alerts I needed the Email Alerts set up before I could create either the process or ...

Security Superbadge -2

Challenge 2: Record-Level Security Settings I created the three user profiles last time, so the starting point tonight was the next tier of security - roles.  I set up the roles per the provided org chart, making sure to follow the opportunity restrictions from the directions. Next, I set up the required user and assigned her to the correct profile and role. Hint:   Use a real email address for Samantha Cordero.  You will need to login as Samantha in order to create an opportunity for her.  While you are at it, go ahead and login to Salesforce1 as Samantha. Once Salesforce1 is enabled, you can set up the appropriate permissions.  You may want to take take a peek at a Salesforce Knowledge Article .   Me - as a Project Manager. Next, I addressed the special role - Project Managers Project Managers require a role, permission set, and a  sharing rule.  Whew! For the final step, I set up the remaining sharing rules in     ...

Einstein Analytics Data Preparation Specialist Superbadge - 1,2,3

Hello all! It's time for another superbadge! I started this superbadge a long time ago... it's time to finish it!  My goal is to complete this badge before my little brother starts to walk.  He's getting close... Step 1 - A quiz.  You're on your own! Step 2- This is one checkbox in setup.  You're on your own! Step 3- Let's talk about that.... Dataflow. The best tool to use when crafting your dataflow is the data monitor.  It can help troubleshoot issues to find which part of the process needs some work. For example.... Why were rows not created? The problem? A box was checked that should not be checked.... The alias name was not correct for the "register" node. Once you see that beautiful green "Success" message, it's time to check the challenge.  Do not be discouraged if you get a few error messages.  This superbadge is EXTREMELY picky on syntax.  A few common errors: You can see this error and st...