Building Reports Like The Awesome Admin You Are

Salesforce events always offer an opportunity to get to know others enthusiastic about the Salesforce platform. As part of Salesforce’s efforts to continue to highlight the excellent work of Salesforce Admins, they’ve carved out the #AwesomeAdmin Zone. Keep an eye out for this area at Dreamforce 2015 as it’s sure to be hopping. If you’re new to Salesforce Admining, it’s a great spot to get some of your questions answered by seasoned Admins who are eager to share their knowledge.

Last week at the NYC Salesforce World Tour I had the pleasure of volunteering at the Reports & Dashboards booth with #AwesomeAdmin and fellow Philly Girly GeekKathy Chicotle. In addition to it being a total blast, it was incredibly enlightening. Answering question after question about building reports and customizations reminded me that there are overarching commonalities regardless of your industry. What are some of those things? Read on.

Start with the Business Process
I can’t tell you how many times I asked the Admin with whom I was speaking what the underlying business process was of the Report we were discussing. The role of an Admin requires much of the same insights as being a Business Analyst. It’s up to you to make sure that the decisions being made fit into the context of your instance. If you ever have the opportunity to listen to Jeff May discuss Admins as BAs, seize it.

When you are building a Report, trust but verify. Ask the requestor to describe for you in plain English what he or she is trying to accomplish with the Report. Often the requestor will come to you with preconceived ideas of how you should build the Report. That’s great some of the times but can also be misleading. You, as the Admin, know your instance and its architecture better than your users. So while someone might be requesting certain Fields or Objects be pulled into the Report, make sure you’re understanding the context of what you’re building. Perhaps there’s a better way to get at that information that hadn’t occurred to your coworker.

If you’re starting from scratch with a shiny new Salesforce instance, take the time to really scope out the reporting needs before you build. Having a clean slate from which to work is a luxury. Enjoy it! If there is already a whole host of Reports, see if there’s a way to add a field to an existing Report to fulfill the need and avoid creating one more Report.

Standardize Naming Conventions
Naming conventions are your friend. There are no sub-folders for Reports & Dashboards so it’s up to you to keep things in order. Reports have a way of multiplying like bunnies if you aren’t careful. The next thing you know, they’re so out of control you don’t know where anything is. Let’s put a stop to that.

My preferred method of organization is to use the basic formula of Heading: Report Name. For instance, if you have built a Report to see how many members are renewing annually and who they are, the Report name would read — Membership: Annual Renewals. Let’s say you also want to see a Report of your LYBUNTs (Last Year But Unfortunately Not This Year) and SYBUNTs (Some Year But Unfortunately Not This Year). Those would be named Membership: LYBUNT and Membership: SYBUNT respectively.

How is this helpful? This will group all of your “Membership” Reports together thanks to the power of alphabetical order. Now, when you go to look for your “Membership” Reports, you don’t have to dig for them or remember what the exact name was. Boom, they’re right there.

Use Standard Salesforce Time Filters
The discussion of LYBUNT and SYBUNT Reports raises another interesting point — how to filter for dates. I’ve seen any number of Reports that have been built with a filter for “2015” or another equally restrictive time period. Whenever possible, use the Range function for dates. This gives you a wide variety of options spanning FY (fiscal year), CY (calendar year), Quarter, Month, Week, Day, and beyond. There are also options to filter for “Next 30 Days” or “Previous 30 Days” as well as other time windows if you want your Report to float with you and not be affixed to a certain month. This will give you greater flexibility as you build your Reports and save you from having to build a new Report every year.

Keep Custom Report Types Streamlined
Do you really need a new Custom Report Type for that? Remember, the more Report Types you have, the more confusing it will become to build Reports. Just as I recommend naming conventions for the Reports themselves, these are also helpful for Custom Report Types. Keep things clean and tidy and use titles that reflect what the Report Types do. You’ll be so much happier in the long run.

Join Your User Group Community
Want a place to ask those, “How do other people do this?” questions? Join your local User Group! Login to the Salesforce Success Community and click on the User Groups tab. This will provide a list of all the amazing User Groups out there. Many of the larger cities also have a specific Nonprofit User Group and a Girly Geeks chapter. Search your city and see what comes up, then go mingle. They’re a fantastic way to meet other #AwesomeAdmins like yourself as well as those who hold other Salesforce roles. Plus, it’s always great to chat with folks who are as enthusiastic about all of this as you are.

Please find the original post on roundCorner's Blog.

Women in Tech: Cracking Open the Door

Since establishing the Philly chapter of Girly Geeks, a Salesforce User Group dedicated to women, there’s a question I’m often asked that I didn’t anticipate: “Why do women need their own group?” At this juncture I do a quick scan of the room tallying how many women are present. By and large I can count them on one hand, five women in a room full of thirty-five people. And I think, “This is why.”

What comes out of my mouth is slightly different. No, women don’t need their own group. Nor do Developers. Nor Nonprofits. Nor FinTech. If you boil it all the way down, we don’t even need a Salesforce specific group.

But we flourish in them. Humans crave community, an environment in which our peers comprehend how we work, the forms successes take, the struggles that we might be encountering, and our specific brand of tech. These groups give us a forum to discuss what’s on our minds in a highly specific context.

But there’s another part of the story — the one that I often don’t delve into when standing in a room full of men. I still regularly find myself the only woman on a team or in a meeting. I’m not unique. This is what women in tech are used to. (I’m not about to delve into diversity numbers. Others have addressed those quite adeptly — TechRepublicSalesforceGoogleFacebookApple. They all hover around a 30/70 split.) I knew what I was getting into and 100% signed up for it. I’m comfortable with this dynamic. But I know there are those who aren’t. These are the women who could thrive in the Salesforce ecosystem but don’t want to be the only woman in a room. By entering, they would bring yet another perspective to the table. One that I’m not completely able to articulate because, honestly, I’m not one of them, but that I know is important.

Sometimes we’re so busy knocking on the door, shouting, “Why aren’t there more women in STEM?” that we deafen ourselves with the noise. What if we stopped banging and stepped back and opened the door letting those on the outside peek into the room? Peering in, they would see me sitting at the table looking over to say, “Welcome. Come join me.”

As more women join us in the room, both the physical and the metaphorical one, we’ll continue to nudge our slice of the diversity pie chart until one day asking the question, “Why do women need their own group?” sparks an entirely different conversation.

Please find the original post on roundCorner's Blog.