Load more data and refine your dashboard

1. Load one month of data

You have been working with only 10 purchase orders, all of them for the same day. You have validated the results of that data. It is now time to see the results of loading a full set of customer data.

Start by importing more orders to your application. 

Step Action
1 On the left menu, click Routes and select the rouOrder route . Your route should be running.
2 Use manual injection to load the Part-4-31-Days.txt data file. You may notice that it takes longer to load this data because it covers 31 days of activity.
3 Once the upload is complete, check the logs to be sure.

2. Validate the data

Now, validate the new data using your Search for Orders dashboard.




Go to the Search for Orders dashboard.


Change the time machine controls to jump to May, 2nd, 2017. Leave the time settings as is, that is 11.45am.

If everything worked properly, you should see 13 orders in he Selected Orders pagelet and 13 orders in the Orders Closed Today pagelet.

Display the number of rows in a pagelet

Validating by counting up rows might not be easy. There is a way to make it easier. To display the number of rows in a pagelet, follow these steps.

Step Action
1 Put the dashboard in edit mode, then edit , the Selected Orders pagelet.
2 On the left menu, click Format .

In the Row Count area, check the Show numbers of row in the title option.

4 Click Done . The title bar for the pagelet now shows that there are 13 rows in the list.
5 Make the same change to the Orders Closed Today pagelet.

Click Save . Your dashboard should now show 13 rows in both pagelets.

Force-start background calculations

If you followed the steps in the previous task without interruption, there may be some unexpected dashboard content.

Open the Overview dashboard. You expect from the Search for Orders content that the pagelets for completed orders and in-process orders will show 13 orders each.

What you are most likely to see is a dashboard with charts and counts all showing zero, which you know is wrong.

The data you've just loaded is data that is in the past. Decision Insight (DI) expects to be receiving new data in real-time (or near real-time), and thus prioritizes the calculation of attributes related to new data. 

Decision Insight does not compute/recompute data from the past, or late data. Only late data that intersects with the active period automatically triggers recomputing.  This prevents massive resource consumption in case accidental late data is imported. 

You can configure the active recomputing period from the Computing options screen. For more information, see Computing options.

The good news is, you can still force start the calculations for past data as needed. Follow these steps.

Step Action

On the main menu, click the Security & Monitoring    icon > Computing.


In the computing monitoring console area, you should see the three computed attributes you've created for the Overview dashboard.

For each attribute:

  1. Click Recompute.
  2. Select the date from which the data should be recomputed, the data from Part-4-31-Days.txt starts on May 1st, 2017, so indicate this date.
  3. Click Apply .

Tip: Once you've started recomputing an attribute, you can click the Refresh button to see whether the recomputing has started and how many corrections still remain.


Now look at your Overview dashboard. The counts and charts should match the Search for Orders dashboard.

Related Links