Databases Reference
In-Depth Information
The steps to implementation
What follows are high-level descriptions of the steps to take to implement the described fulfillment
report.
determine data sources and importing data
In this example, there is data ready for reporting. Because the data server developer understands the
need for a report and existing SQL Server Reporting Services (SSRS), reports are already supported
by the data he manages; thus, this is not as difficult process. Of course, every use case is different and
data preparation might be more work-intensive.
Import data into PowerPivot, explore data, and design
PowerPivot in Excel 2013 is the choice for creating proof-of-concepts and for making ad hoc reports.
Users are able to schedule a data-refresh in SharePoint. Sometimes, the next logical step is to formal-
ize the PowerPivot report by importing it into the tabular modeling tool in SQL Server Data Tools
(SSDT). At that point, you can automate a data-refresh (or processing) on a more flexible schedule.
You will find that exploring data in the PowerPivot window is fast and simple. You can filter on
columns and quickly determine what additions should be made to the model by way of calculated
columns and measures such as calculations.
In this case, the SQL table already updates the all-important date/time stamp for each status of the
fulfillment process. Occasionally, however, you will perform a Data Analysis Expressions (DAX) formula
to enrich the data. Figure 1-7 shows is an example of a simple calculated column to provide in a Pivot
Table or Power View the duration of time from when the PO was created to Rendered (or printed), in
a user-friendly format.
FIGURE 1-7
PowerPivot Window and DAX for showing time between PO and Rendering.
Here are the equations used to calculate Seconds, Minutes, Hours and Days.
Days:
=IF(ISBLANK([Rendered]), 0, FLOOR(1. * ([Rendered]-[PO Assigned]), 1))
Hours:
=IF(ISBLANK([Rendered]), 0, FLOOR(MOD(24. * ([Rendered]-[PO Assigned]), 24), 1))
Search WWH ::
Custom Search