Scribd
Upload
31 views

Using Ssas 2005 As Ds For Power Pivot

Measures imported from SSAS cubes into PowerPivot are imported as text columns instead of numeric columns as expected. This can cause incorrect aggregations when the measure is actually a count or number. There are also issues with locale settings causing errors when initially changing the data type to numeric. The recommended steps are to change the data type to numeric, refresh the data to fix any locale issues, and check for errors during initial data type conversion. A better method is to temporarily add a slicer returning no rows, change the data types, then remove the slicer to avoid repeated loads or conversion errors.

Uploaded by

exbis
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
31 views

Using Ssas 2005 As Ds For Power Pivot

Measures imported from SSAS cubes into PowerPivot are imported as text columns instead of numeric columns as expected. This can cause incorrect aggregations when the measure is actually a count or number. There are also issues with locale settings causing errors when initially changing the data type to numeric. The recommended steps are to change the data type to numeric, refresh the data to fix any locale issues, and check for errors during initial data type conversion. A better method is to temporarily add a slicer returning no rows, change the data types, then remove the slicer to avoid repeated loads or conversion errors.

Uploaded by

exbis
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 1

Using SSAS 2005/2008 as PowerPivot Data Source: Measures Are

Imported as Text Columns


Every measure imported from a SSAS cube is imported as a Text column instead of as a Numeric
column. This is very annoying because users are used to use SSAS data with rich metadata, and a
measure is usually numeric. Moreover, the standard aggregation used by PowerPivot for a Text
column is Count - whenever the measure is a real count (thus, an integer number), this is completely
misleading because the user doesn't recognize it is returning a completely wrong value.

Moreover, there is a wrong use of Locale settings and conversion to decimal value gives an initial error
whenever the local settings doesn’t use “.” as decimal separator. However, refreshing data everything
is updated correctly, but the problem is that end users might stop their work before trying to refresh
data after they changed the data type of each measure column to the right type.

Thus, this is the check-list to follow whenever you import measures from an existing SSAS cube to
PowerPivot:

 Change column type to Numeric (all measures are imported as Text by default)
 Refresh data – initial conversion of decimal and thousands separator might be wrong (because
the string is converted to a numeric by PowerPivot, and differences in Locale settings might be
the issue in this conversion), but after you fixed the data type, the following refresh query the
cube again and returns the right value.

More on importing Measures from SSAS cube in #PowerPivot


Several months ago I wrote about the issue importing measures from an Analysis Services cube in
PowerPivot. The short story is that, when you define the MDX query, all columns are imported as Text.
Of course, this is not a good thing for the numeric measures. The workaround is to change Data Type
and then refresh data of the table. However, you might have two issues:

1. You import the table twice. If loading data requires is long, this is twice long
2. You might have an error in conversion when you change Data Type of the column (because
existing strings cannot be converted correctly into numbers – changing Data Type the
conversion happens on these strings, while another code path is executed when you refresh
data from the data source having a column already defined as numeric).

The best thing to do in order to avoid both issues is:

 Define your MDX query adding a slicer that will return no rows in your table
 Change data type of the imported Measures in your PivotTable columns
 Change the MDX query by removing the slicer

I hope this will be fixed in the future, anyway.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy