Reflecting on 1 year in business

It doesn’t feel like it’s been a year since Taking the Freelance Plunge was published but time flies.

Overall Thoughts

Overall, the experience has been positive. I can’t remember being happier and less stressed, professionally or personally, despite the occasional “where’s my next client coming from” setbacks. My only regret wish is that I had started sooner. A few years ago, my employer had kindly arranged a career coach to interview me to figure out what I’d like to do. While speaking to her, I said “start my own business” and it just felt right. I didn’t get into freelancing until a few years later though. Oh well.
Want tips on getting started yourself? Check out Tips Getting Started in Freelancing. Also, feel free to Contact Me privately and I’ll give ya feedback.
Want tips starting your own Salesforce Blog? Check out Bob Buzzard’s Starting Your Salesforce Blog by the one and only Bob Buzzard.

What’s New

Awesome Client Still

Still have an awesome client. They are great to work with, the work is interesting and varied, and I’ll keep working with them as long as they’ll have me. I hope I get to be onsite again soon.

If I ever felt like being a full-timer again, I’d seriously consider these guys too.

Part-Time Work Halted

For a while, I was doing part-time as needed work for a client but they haven’t needed my services for a while. It’s a bummer because they had some very interesting and challenging technical work and are also great to work with. That’s ok though because the work I can’t take on, I usually forward to them along with potential job candidates because if full-time appeals to me again, I’d seriously consider working for them.

More Lightning

I’m now feeling comfortable with Lightning aka over the hump. It still feels like a beta to me because of the amount of developer plumbing needed to make simple things work but that’s ok. Also, I’m starting to like Javascript again but I’ll save that rant for possibly another blog post.

Contributing to Open Source

I’ve always contributed to open source projects occasionally. My focus lately has been contributing to Boostr for Salesforce, which is a Chrome Extension that enhances the Salesforce experience in various ways. “View Offending Process Builder or Flow” Link in Lightning and Field History Tracking Counter Configurability are two features I’ve implemented that are now released. It feels good to know that I’m contributing to the Salesforce world and helping others out. Getting some recognition and thanks is icing on the cake.

What’s Next

Aspiring To Becoming a Salesforce MVP

Recently, I started seriously researching what it takes to become a Salesforce MVP. I even reached out to two of them that I know and they gave me some really good feedback. Essentially, they said to contribute to the community and be very active in it too through whatever means you like such as blogging, social media, user groups, open source, or some combination.

This is a long-term goal and may take years but I think I’ll eventually get there. To help accomplish this, my plan is

  • Increase blogging frequency
  • More active in the community with social media, other blogs, user groups, etc.
  • More open source projects

Through these activites, I’ll be also accomplishing the “Keep Expanding the Network” that I’ve been writing about for a while.

If you have other tips on becoming an MVP, please let me know.

Also, if you feel like nominating me, please do so at Salesforce MVP Nominations which are open through August 7th.

More Open Source Contributions

I’ve been having a blast contributing to Boostr and am going to focus on some other projects too. Stay tuned…

How’s your business or professional goals going for 2017 and how will you reach them? What’s your experience with freelancing been like?

Related Posts

Coming Soon to Boostr: “View Offending PB or Flow” link in Lightning

In BOOSTR: VIEW FLOW OR PROCESS BUILDER CAUSING ERROR, the “View Offending Process Builder or Flow” link works in Salesforce Classic BUT not in Lightning Experience (LEX).

I implemented the Boostr code so now it will. A future release, coming soon, will have this functionality.

Technical Bits

This Boostr Pull Request shows how it’s implemented in Javascript.

High-level Algorithm

  1. If in Lightning Experience, add a mutation observer that reports whenever a DOM element is added or removed on the page.
  2. When the DOM changes, is the Flow Error text added?
  3. If yes, create the “View Offending Process Builder or Flow” link and append it to that error message node.

Why It Didn’t Work in Classic?

The reason is the way that Boostr for Salesforce works. When a Salesforce page is opened, it inspects which page is opened and adds the page specific features to it. For example, when the generic flow error is opened, it adds the View… link. It doesn’t look for changes to the page.

In Lightning, since it’s a Single Page Application (SPA), the page is loaded and then dynamically generated via Javascript. A new page isn’t opened when you click different links and buttons. You’re still on the same page but its contents change as different actions are performed. Since the generic flow error page is never loaded, that’s why the link never showed.

Have a feature you’d like to have in Boostr? Submit a feature request issue in GitHub and a contributor may implement it. Or you can implement it yourself by following the Contribution instructions.

Coming Soon to Boostr: Field History Tracking Counter Configurability

Lately, I’ve been cutting back on tv. Instead, I’ve been reading, hanging with friends and family, and occasionally contributing to side projects.

Today I focused on implementing the Field History Tracking Counter doesn’t take limit increases into account Boostr Request in Boostr for Salesforce.

By default, Salesforce only allows up to 20 fields to be specified for field history tracking per object. However, that limit can be increased, by purchasing more from Salesforce. Boostr was hard-coded to only think 20 was allowed.

Allowed # of Field History Tracking Fields Configurability

Boostr has been enhanced to allow one to configure how many field history tracking fields are allowed on the options page of Boostr.

In the example above, I’ve increased the limit to 40 and saved it. When configuring the Field History Tracking Fields for an object, the label shows how many allowed fields can be tracked based on the setting.


  • This hasn’t been released into Boostr yet but hopefully should be soon!
  • Also, if you’re working in multiple different orgs where the limit may differ, you may want to update this setting to reflect the current allow number of fields. However, this is probably not an issue since most orgs usually only have 20 and that’s what the setting is defaulted to be.
  • I tried to find a way to programmatically find the number of allowed fields but their doesn’t seem to be a way to do this through an API or otherwise. If someone knows a way, please let me know!

Boostr: View Flow or Process Builder Causing Error

Boostr for Salesforce is a Chrome extension that enhances the Salesforce experience by providing various enhancements to the browser experience such as

  • Changeset searching and filtering
  • Checking all edit and view field permissions in profiles and permission sets
  • Counting the number of fields checked in field history tracking
  • and More!

View Offending Process Builder or Flow Link


Now, I’m happy to announce that Boostr has a new feature in version 0.91 and above that adds a “View Offending Flow or Process Builder” link to the generic Flow / Process Builder error page in Salesforce classic. Opening the link opens the Flow Designer page with the Flow or Process Builder that caused the error.


The feature parses out the flow version error id and then appends that to the flow designer page to form the URL to navigate to.

I created this because sometimes you don’t receive the Flow error email and it can be troublesome to identify which Flow or process builder caused the error.

Note: The opened Flow Designer may have actually opened a process builder and not a Flow so be aware of that. The reason is that process builders are really Flows under the hood. When viewing a process builder from the Flow Designer page and reading the error email output, it actually makes more sense.

Thanks Matt

Want to give a big shout out to Matt Simonis who originally created Boostr and who has allowed me and other contributors to enhance it further.

If you’d like to contribute, fork the Boostr GitHub project, make the desired changes, and then create a pull request.