The lifecycle of a business intelligence implementation - Business Intelligence in Microsoft SharePoint 2013 - page 94

Note In Figure 3-32, you will notice two icons in the upper-right corner, users can create a
Power View report or open an Excel file that is connected to the data you provide from de-
ploying a tabular model to Analysis Services in tabular mode.
FIGURE 3-32 BI Semantic Model Connection.
Tip After you begin to add more Power View and Excel reports and then BISM connection
files, your library (list of reports) might begin to feel cluttered. By using SharePoint 2013 list
features, you can do things such as add a Yes/No column called “Show,” select the check
boxes for those that you want to show, and then modify your default view to filter on the
“Show” column.
Summary
This chapter provided an overview of the major steps involved in getting to trusted data by using SQL
Server 2012, SQL Server Data Tools, and SharePoint 2013. Keep in mind that ensuring data quality
throughout an organization or even in a department is a process rather than a single event or initia-
tive. The process, showing the connection between the BI developer, end-user, IT support roles, and
tools, was summarized in Figure 3-1 at the beginning of the chapter.
Creating a repeatable ETL process and getting data from disparate sources to a staging database
and then to the data warehouse is a time-consuming process and might be accomplished by another
team. This does not stop you or your team from benefiting from data that is not yet stored in the data
warehouse and can be explored and used to create proof-of-concepts, prototypes, reports for deci-
sions that must be made more quickly. The tabular tools described in this chapter and topic introduce
a much faster life-cycle to implementing business intelligence across teams and the organization.