Report building in Power BI to some, is viewed as a work of art. To be a successful report builder, you should not only think about the design of the report, but should also focus on how the solution will be viewed in different aspects by the end-users. In this blog post, I will be exploring some of these ideas and how to think more about the end-users.
How easy is it to see an update in Power BI? Well, it’s easy to see posts about what is being changed or added, but it may be more difficult to understand the changes and know what they will do. Reading something and understanding something are two completely different things. In this blog post, I’ll take an in-depth look at a few of Microsoft's latest updates to the Power BI platform. It may be helpful to have had a fair amount of exposure to the Power BI platform before reading this post.
Recently a client came to us to see if we could help them automate their RFP distribution system. Currently the client has an employee manually check several websites for RFPs and alert the appropriate business vertical when a relevant RFP is found. The current system requires manual data scraping, meaning the process is slow and results in RFPs being missed. For the proof of concept phase with the client, we decided to build a machine learning model to classify the RFPs correctly and provide a way to automate the routing of the RFPs. The client wanted to break the project into stages so once the initial Proof of Concept was successful, other parts required to automate the whole process would receive the go-ahead. If you would like a proof of concept, visit our Business Analytics page for information.
Microsoft has just introduced dataflows to Power BI service which they see as the next step in the self-service revolution Microsoft began with Excel. Dataflows incorporate the necessary ETL steps and allows other people to access and work with the dataflow. Think of dataflows as power query on steroids with the capability of multiple users to take advantage of a centralized ETL operation on data.
What is Common Data Service?
Common Data Service is a cloud-based data storage and management system that standardizes your data across business applications like Dynamics 365, Office 365, mobile apps, and Power BI.
Your data is stored in standard (or customized) entities, similar to how a table stores data in database. If you use Common Data Service, your suite of business applications feed data predictably to these entities, allowing simple data sharing, data mining, and business intelligence.
This dashboard probably looks very familiar to you. You might have five or six dashboards you’re watching for ebbs and flows, spikes and surges. Maybe you have a very advanced process that involves downloading data into Excel and mashing different channels together. But that doesn’t sound very advanced, does it? Manual data entry? Staring at four online dashboards, commenting on "this one is up, or this is down"? There’s nothing advanced here. It doesn’t tell you how people responded, how their interactions lead to anything. Do you let your marketing data impact future creative decisions? If it's not producing marketing intelligence, your marketing data is completely useless.
"Last night, we had a happy hour to celebrate burning Joe's Excel spreadsheet."
Those were the exact words out of the mouth of the Director of Marketing at a global med-tech company based in Minneapolis. Just a few months earlier, Beyond Impact helped deploy a Marketing Intelligence Solution leveraging Power BI to migrate an Excel spreadsheet that essentially ran the entire Retail Marketing division. This Excel spreadsheet was held together with duct-tape and elbow grease, leading the client to say, "there has to be a better way to work with our marketing reports."
Growing up in a small town near Lake Mille Lacs, a good 90-minutes north of the Twin Cities, much of my learning as a little boy happened in a sandbox. Not the giant plastic turtle you see in Walmart today. Rather, an oversized wood structure filled with sand and a collection of old metal Tonka Trucks. I would spend the summer days building roads, bridges, castles, and rivers. I engineered high-security prisons for frogs I caught. I threw sand at my older brother and occasionally we tangled with a garden hose, much to my mother's displeasure. Every night I'd come in for dinner covered head to toe in dirt. Little did I realize, I spent those long summer days learning physics and engineering in the sandbox. I've always learned by just digging in. My childhood story really has nothing to do with Power BI - it simply points out the fact we can learn so much more when we get our hands dirty.
During my recruiting days - I naturally sought the thrill of chasing down the nearly impossible candidate. The type of candidate with a minimal digital foot-print, and a LinkedIn profile of fewer than 60 followers. The bulk of my time was spent seeking the ever-elusive mobile developer long before anyone had heard of Xamarian. Well before Microsoft's acquisition of the mobile cross-platform tool. Coffee meetings, technical user-groups, tossing around astronomical salaries. Or so I thought at the time. Emerging technology was driving this market and every organization was desperate to discover adequate talent.