Wave Analytics & Extra Objects

Wave Analytics and Extra Objects

By Billy Weisgerber

In a previous blog post, we talked about how to generate YoY and MoM Reports & Dashboards utilizing formula fields and applying those as filters. In this blog post and an upcoming post, we will be walking through how to create a custom dataset, how to create your own dashboard, and how to edit a standard dashboard using Wave Analytics.

A lot of times, you need to include Standard & Custom Objects alongside of the standard data that Wave brings in with their Standard App creation. Luckily, within a few clicks, you can have a new dataset to include in your Dashboards. For this blog post, we will be utilizing the Standard Object, Orders and its Child Object, Order Products.

Creating a Dataset

If you have never created a Dataset before, don’t worry, that’s why you are reading this blog post, right? If not, keep reading, you may learn something new. When creating a Dataset, go to the Wave Analytics App, and click the blue Create button and click Dataset.

Search-Wave-AnalyticsThis will start what I call the Dataset Wizard, first click the Salesforce icon. As you can see, there are multiple ways that you can pull in data for Wave Analytics, but we will be focusing this post just on Salesforce. You can enter a Dataset Name, and select the App that you want the Dataset to be stored in, but please note that you will have to re-enter this after selecting the fields and relationships for your dataset.


When selecting the starting object, you want to start at the bottom and work your way up from there. For example, since Order Products are the Child Object of Orders, we would want to start with Order Products, and access the Order Data via a Lookup or Master-Child relationship. This is the opposite from how Custom Report Types are created, working from the top to bottom. For example you select Orders and the next level would be Order Products and you select whether or not Orders must have Order Products, creating the Venn Diagram relationship.


Once you have selected your starting object, you can then build out your dataset with fields and relationships.

  • In order to start, hover your mouse over the object and click the + to view Fields and Relationships. If a specific field is not available in your list, you will have to check the security for yourself and for two Wave Analytics Profiles, Analytics Cloud Integration User and Analytics Cloud Security User, and ensure each of those have access.
  • As you Join a relationship with another object, you can also add fields from those objects.


Some good questions to ask are, what will this dataset be used for? Is there any data beneath my current starting object that I need? What relationships are needed, and what key data do I need from each of those? With that, below is an example of what you can have put together for a dataset. As you can see, the number of fields decrease as we go up the “hierarchy” in relationships. The reason for this is because the further you go from the source data, you normally don’t want excessive data, muddying what the true focus is for the dataset.

Once complete, click Create Dataset, input your Dataset Name and select the App that your Dataset will be stored under. The App will default to My Private App to ensure that any Datasets that are a work in progress are stored there, but if you are confident in your Dataset creation skills, you can set it to another App.

Congratulations! What you have just created is the JSON to be added to your Dataflow and once ran, the Dataset will be made available for use in Lenses and Dashboards. If you want to go ahead and start testing out your Dataset, be sure to run the Dataflow that it is appended to, and click the Dataset inside the App to start building out a Lens. Stay tuned for our next post on Creating Lenses and Dashboards in Wave Analytics.

Leave a Reply

Your email address will not be published. Required fields are marked *