The main need is being able to pull data in from various cube sources. The more you know about the different sources, and the ways in which the data relates, the quicker you can build out the model. The definition of done, for this step, is to reproduce any manual reports or external sources from the new sourced data. By being able to go under the hood in the various cubes and databases, you can quickly render data models around specific perspectives (partner, customer, product, segment) focusing on revenue, adds, customer counts, etc.
Most of the data is already live somewhere in the Microsoft data ecosystem, be it MSX, MS Sales (brought into business unit cubes – analysis services) via the Azure Health Report, BizApps Cube, Rescube, etc. Most partner information is in the OCP data marts (One Commercial Partner) including CRM, Performance, INsights, etc.
What most clients need is for someone to stand in as a proxy for their own reporting teams. Typically they have deep backlogs and limited time to add new features, so there is minimal business case made to build new things. Prototyping out data from existing sources in order to begin tweaking it to match client expectations is a big part of this engagement. It’s what we do naturally.
One of the things I have found brings me a great deal of success is to just open up a data model and start looking around. However, often now the teams also include Data Dictionaries, which can help to navigate the cubes. But often the connection you’ll find in Excel will be slightly different from a pre-built Power BI connection. The difference being subtle, but often confusing.
Understanding how to dive into and out of databases and cubes, whether through SQL Server Management Studio, or via Power Pivot in Excel, or Power BI Desktop, is the key part. There are lots of videos and tutorials on data acquisition available, but the need here isn’t for someone learning to do this to “learn on the job”. We need someone who knows HOW to build data models, and who only needs to learn the landscape of the new environment. What keys, measures and dimensions are available.
In short, Neha needs someone who can understand the business requests being made, and relate them to the data sources available in the Microsoft ecosystem. For the partner program there are a number of sources that relate to the different phases of the partner relationship. Readiness for training and certification, with # of individuals trained being a key indicator of partner capacity to build and sell solutions to customers. Performance is another one, as in, is the partner actually selling products to customers? Solutions catalog is another. And CRM aka Partner Pipeline is another.
Being capable of navigating all of these pieces is critical to our success here.
In other news, I’m tired as fuck and pissed off that I haven’t been able to write about my own stuff for days. I haven’t even done any RTVs either. So basically I’m paused, waiting to press play.
I’ve had vision for a number of things. BUt I’m a fuvcking idiot so who the fuck cares.
Oh god, what is that voice of doubt? Why the fuck is it here? Who let it in?
Narrative.
What we need is someone who has used Power BI by going into the Advanced Editor in Power Query and tweaked connections, remapped objects, etc. Using the interface is important.