In the sprit of post about relationships, today let's talk about Report Types and Fast Food.
For those that are not familiar with what a report type is, it's a neat feature of Salesforce that lets someone with special powers join different objects in Salesforce. Let's say you can run reports with Account and Opportunity or Order and Order Products. But, it would be super cool if you could build a single report with fields from all of those objects. All of us hate joining reports, and there only seems to be one person who knows how to. This can help in those situations.
What is even more cooler (not a real word), is you can bring in fields from even more objects that are not a part of the ones in your new fancy report type using lookups.
So whats the problem? Sounds amazing right!
Take a small amount of time to come up with naming conventions and ownership. This area of Salesforce, if left unattended, can soon begin to cause a lot of drama.
1. You can name a custom report type ANYTHING, and this leads to a LOT OF CONFUSION. Just follow the Salesforce method that is used for everything else - X With Y With Y. Go back and update your report types using this convention. A few minutes will save you countless calls and meetings.
2. EXPLAIN the word WITH to everyone. This is critical!. When you are at the drive thru and you order your favorite burger with pickles. It comes with pickles. It does not come with a compliment of optional sides in case you forgot to order them. If you did not ask for it, it will not be placed on your burger.
With means that there is a relationship between the two objects, a special bond. Meaning, a row in your report will only show up when there are records from each object. Example: you have 546,988 Accounts and 345,678 Opportunities. When you run a report of Accounts and Opportunities with fields from both, you can not exceed 345,678 results. Salesforce does not allow blank results when your Account has no Opportunity.
3. What if you want blank rows? Well, again, this is where Custom Report Types can help. You can indicate With or With Out when you build it. But, remember to make that clear in your naming. These names show up to your users. Use W/O and ensure the description explains the difference.
4. Include the abbreviation (CRT) in the label name. This helps everyone know they are using a Custom Report Type. So, when complaints come in about point 5, missing fields, you know how to find which report type.
5. Assign someone the duty of ensuring fields are maintained on your Custom Report Types. You could even add it your deployment checklist, should you have one. There is nothing more frustrating than hours and hours of troubleshooting security/profile settings. To then realize the field was never added to the CRT. New fields do not get added automatically.
Start with this simple tips and you will be well on your way to avoiding potential adoption issues around reporting and data.
While I am all about personal development, and relationships. This blog is more aligned with the ones in your Salesforce Org than with yourself or others.
Knowing what objects connect to each other and how, is vital in reporting, integrations and so much you or others need to do.
Keeping a diagram up to date seems to be a never ending nightmare of blocks and lines. If you have OCD tendencies like myself, you can get lost in lining things up for hours.
Salesforce has a scheme builder, but wait you can't export it nor save the layout. Since we are being candid, I would rather eat glass than use this for an ERD (Entity Relationship Diagram).
How about in 5 minutes you could export all of your fields from all of your objects, and have a tidy list of lookup fields?
Stop relying on diagrams and potentially outdated data model documents and pull down this information real-time. Then teach others how to interrupt the results. Everyone will love you and you won't have to produce a single diagram.
1. Head over to https://cloudtoolkit.co/
2. Use the Scheme builder, and when it finishes export the results into a single tab Excel version.
3. Sort your field type column by field type, and boom!
The simple way to teach everyone is that the Object on the left is looking up to the object on the right in the type column -"Child to Parent".
Another training point is that if you send this to users that are building reports, most of the time the report types will follow the same pattern as in this spreadsheet - "Object With Object".
By the end of 2020 the long awaited Recycle Bin will finally make its way to the Lightning Experience!!!
No longer will you have to switch back to Classic mode!!!
Scheduled for Winter 20!
Another amazing day in the Salesforce Ohana!!!
Taveza's 'Learn Flow and Auto Generate Orders' app showed up during the TrailheaDX conference!!!
Salesforce has introduced a new AppExchange category to allow partners to publish what are called Flow Templates.
Now you can modify Flows from a managed package! Awesome way to learn flows via an easy to download app with several examples! Deep Cloning, Auto-Generate Orders, Email Faults and much more! And yes, FREE!!!!
Originally Posted In 'Inside The Salesforce EcoSystem'
My Salesforce journey started 12 years ago while working for a major cable company. A small business unit had implemented Salesforce, and it soon became the corporate standard. I jumped at the chance to expand it to over 5.000 users across North America. Within two years, I had designed a custom CPQ and order management solution, integrated into 18 billing systems. An accomplishment still in place to this day.
From that point forward, I was hooked.
I ventured into consulting so I could broaden my experience across multiple verticals. While I loved designing solutions that were deemed “not possible” and pushing the limits of Salesforce, growing inside of me was a deep desire to share the knowledge and experience with companies that were just starting out. I wanted to build an app!
Years went by, and finally, I decided it was time to stop thinking and start acting. I quit my job, took everything I had, and bet on myself. I signed up to become an ISV partner and started building — each day getting more and more excited. I was finally taking action and doing something in life I wanted to do.
Then, the other day, I glanced at a new email that popped up on my phone: “Congrats! Your Application Passed Security Review.”
I broke down and cried. That message was the final approval required for a listing on AppExchange. Months and months of work came to an end with one simple email. Yet, the dream behind it was years in the making.
The journey to this point has been an amazing experience. I’m not certain what’s next, or how successful this or other apps will perform in the market. But as I look back at what it took to get this far, there are a couple of things I wish I knew and I want to share them with you:
You never know if you have something real, and you are the person creating the next niche.
For many of you who know me, I've had a dream of being published on the Salesforce AppExchange for many years. Well today, that goal has finally become a reality! While my first app in publication wasn't the plan, none the less I actually achieved my dream. Last year I finally decided to 'bet on myself' and take the plunge. The journey has been amazing and I can never look back on this experience with any regrets.
Along this path, it has been filled with excitement, fear, sleepless nights, self doubt, silent victories, and many other emotions. Building an app was the 'easy' part. Playing the role of product development, strategist, marketing, operations, and many of the other functions have been the hardest on most days. I realized I have been my own worst 'client' when it comes to requirements and 'sticking to scope'. Giving me an even greater appreciation for the consulting work I have done.
I have reached out to so many people along the way, and I can't begin to express my gratitude for your feedback and support. Coach Ty Vincent, thank you for the push and continual kicks along the way.
While many of us have dreams of starting our own software company and retiring in wealth and fame. For me, it has been about taking my creative sprint and channeling that energy into something constructive. Yes, of course, I hope to become successful and make a living. But, along this path things changed in ways I had never considered.
During this process, I took time to involve my children along the way so they could learn what their father actually did for a living. Mackenzie Stall, my oldest, performed my QA and UAT, providing invaluable insight into the workings of the 'Millennial User'. I had my 11 year old son, who was completely new to Salesforce, download and set-up one of my apps in under an hour. While the middle two were just happy to be able to use a computer playing with Gantt charts.
With those shared family experiences, it hit me. Not only was I able to show and involve my family in my project. My children were also able to see their father set goals and make them happen. A first hand account of seeing a dream become a reality! Being able to explain to them that regardless of the success or failure, you never know what will happen until you try. That it takes hard work, long days, and a disciplined approach to even begin to answer the question - 'Can my dream become a reality?'.
For this part of the experience, being a father and teacher, was the most amazing of all! This is the true legacy I am so proud to have accomplished by embarking on this journey.
I welcome all of you to please reflect, share, like, and comment on this post. Of course, you can also check out my first AppExchange app too!