Professional Documents
Culture Documents
Using Ssas 2005 As Ds For Power Pivot
Using Ssas 2005 As Ds For Power Pivot
Using Ssas 2005 As Ds For Power Pivot
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.
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).
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