8

The Debug Log is like a savior in Salesforce hell.

Comments
  • 4
    I see you're finding your way through the mayhem.

    Next up, queries outside of that shitty console that likes to not work most days.

    https://workbench.developerforce.com/...
  • 1
    @C0D4 Yes. Seems like I understand the basics now in some way.

    For example, today I was working on the Process Automation Superbadge and was unable to pass one of them. But then I suddenly found myself looking into the debug logs, and found the issue (a entry criteria was being evaluated to false).

    The fact that I didn't panic all over the internet looking for solutions (like I would have done 2 weeks ago) made me happy.

    Thanks for the support!
  • 1
    @nanobot those logs save lives.

    Be deliberate with adding system.debug() in places, some things are painful to work out.
  • 1
    @C0D4 cannot stress this enough.

    Salesforce policy management is a god damned nightmare and accounts for at least 40% of my frustration.

    If your dev tools don't match 1:1 with your API, then your product is trash.
  • 1
    When Salesforce released sfdx couple of years back, we were excited in our team because we will get to create dedicated environments for development isolated from others and everything will be bright. It was such a nightmare converting old classes to sfdx compatible packages. It was so tiresome that we eventually got rid of it and we are still developing the old way. And we dont have any courage to pick this thing again.
Add Comment