“Hey, come, have a look I came up with something very smart.” My eyes start glowing and I become happy like a little child that discovered a shiny rock. While that excitement is important, it keeps me motivated, that feeling is also a warning sign. My “Smart Ideas” are 99 out of 100 times, not …
Continue reading “Opinion: Smart Idea != Good Solution (mostly)”
Topic: Using Custom PermissionsTarget Group: Admins, Architects & DeveloperComplexity: Medium Who does what when why?These simple questions guide our requirements. Once the solution is implemented it becomes (almost) the wild west. A finance User updates Opportunities for Sales, the Service User orders products and the Marketing Intern deletes Leads. We try to keep on top …
Topic: WITH SECURITY_ENFORCED, stripInaccessible and Schema.DescribeSObjectResultTarget Group: Developers, ArchitectsComplexity: Medium Going down the ISV route taught me an important lesson, enforcing Field and Object Level Security is much easier than thought. As we all know, APEX runs in System Mode, great in some cases but really bad in most cases (IMHO). I’d love to have …
What better way to finish up this year than to see where I stand with my next big adventure: Easy-CPQ. The MVP features are mostly complete (90%). Next is code review, lots of testing and refactoring, especially the JS code is badly structured, too many dependencies. Once this is done, I’m looking for companies to …
Topic: Numbers, learnings and plans for AppExchange “Admin’s Helper”Target Group: (Aspiring) AppExchang ISVsComplexity: MediumThe end of the year is a good time to take stock of my AppExchange business. Maybe my learnings encourage and help others on their way to the AppExchange. Numbers: Apps released: 4 (3 paid, one free)Active prod. installs: 120Most popular App: …
Topic: Check-Up after feature deliveryTarget Group: Admins, In-House Consultants or SF Product OwnersComplexity: Easy I’m always scared, scared that what I’ve built does not properly work, stops working, or is not used.As an in-house consultant, I tried to follow the 1-7-28-84 rule.After 1 day, 7 days, 28 days, and 84 days I check if the …
Continue reading “Post: 1-7-28-84 OR Why Done is not the End”
Situation:For Super-CPQ I want to display Product Details in a nice LWC. Old Attempt:LWC Controller calls “APEX controller Class”. Controller gets Product Details from Database transforms it and returns the Objects Product and Pricebook as type sObject to LWC.The LWC Controller does some more transformation. Problem:Every time I need a change it was a game …
Continue reading “First Attempt: Layered & Contract Driven Software Architecture”
“People think they need a multi-org environment when all they need is to architect their code a little better.”Matthew Gerry He got me thinking, what other bad reasons I’ve heard for going down the multi-org route? 1) Departments can’t agree on priorities-> Departments will not agree on priorities in a multi-org environment as well.2) Too …
Continue reading “Opinion: (Maybe) Bad reasons for Multi-Org”
Take-Away: Don’t create an app if you are not willing to become a service superstar. Ed Ralph, Bram Julsing or Tim Mathis, all of them built a successful AppExchange business over the last 2 years with many 5-Star reviews.I was curios: What are people saying about their products? While all reviews mention the great product, almost all have …
Continue reading “Service, Service, Service OR the secret to 5-Star reviews”
I’m lazy, especially when I’m coding, but it always hurts eventually. I’ve a simple example requirement:Make a Call-Out to a backend Service and save the result in a record. What I did:I have a nice and tidy invocable method that makes the call-out and saves the result as a record.I added that method to a record …
Continue reading “Single Responsibility rules OR why the lazy way hurts (eventually)”
