Microsoft Excel 2013: Building Data Models with PowerPivot

Errata for Microsoft Excel 2013: Building Data Models with PowerPivot




The errata list is a list of errors and their corrections that were found after the product was released. If the error was corrected in a later version or reprint the date of the correction will be displayed in the column titled "Date Corrected".

The following errata were submitted by our customers and approved as valid errors by the author or editor.

Color Key: Serious Technical Mistake Minor Technical Mistake Language or formatting error Typo Question Note Update



Version Location Description Submitted By Date Submitted Date Corrected
Printed
Page 29
Label for Figure 1-30

Figure 1-30 uses the same text label as Figure 1-29. It requires a text label specific to that image.

Note from the Author or Editor:
The description of Figure 1-30 should be changed to: Office and SalesManager have been added to the report.

Zack Cataldo  Aug 27, 2013 
Printed
Page 29
Chart (only one on page)

Figure 1-30 (Page 29) and Figure 1-29 (Page 28) both have the same caption The Categories table is now a column chart

Note from the Author or Editor:
The caption of Figure 1-30 at page 29 should be changed to: FIGURE 1-30 The Office and SalesManager tables have been added to the report.

lestersal  Jan 12, 2014 
Printed
Page 191
3rd full paragraph

The book reads "In Figure 7-10 you can see the calculated column defined in DimProduct, where the table has been sorted using ListPrice ascending." The table has actually been sorted by ListPrice descending, or ListPriceRank ascending, but not ListPrice ascending. Thank you. Arthur Jenkins

Note from the Author or Editor:
Correct, the phrase should end with "where the table has been sorted using ListPrice descending"

Arthur Jenkins  Oct 11, 2013 
Printed
Page 191
United States

This is not an error as such but a suggestion to remove what I believe is some ambiguity in the discussion of the Earlier function at the top of P 191. The text is: "Thus, the row context in Filter is nested inside the original row context introduced by the calculated column, which results in "it" being hidden in the innermost expression." I believe that the authors could have written this more clearly. Again, they say that "the row context in Filter is nested inside the original row context introduced by the calculated column, which results in it being hidden in the innermost expression." When I read this I thought "the row context in Filter is nested inside, so it is in the innermost position, so the row context in Filter must be hidden. But it's actually the original row context introduced by the calculated column that is hidden. Perhaps going beyond using the word "it", and actually spelling out which context is hidden, would be more clear, or somehow avoiding the use of "inside" and "innermost". I hope that this is clear and that I am correct about my interpretation of the meaning of this concept. I am taking the time to mention it because it is a somewhat complex topic that I struggled with for a while. I think these authors are great. Regards Arthur Jenkins

Note from the Author or Editor:
Please, change the sentence in: "Thus, the row context in FILTER is nested inside the original row context introduced by the calculated column, which results in the outer filter (the calculated column one) being hidden in the innermost expression"

Arthur Jenkins  Oct 11, 2013 
Other Digital Version
739
fig 2.5

The Access table names downloaded from http://examples.oreilly.com/9780735676343-files/ is different from the book. For example, fig 2.5 refers the tables as Dimxxx and Factxxx, but the downloaded table names are Production_xxx (which is the names used in Excel 2010).

Anonymous  May 23, 2013