December 2007 - Posts
UPDATE: Version 2 details can be found here (Link below updated)
Being a non-accountant type, choosing the right account type for members of the account dimension was a little bit of 'trial and error'. After much hair pulling and frustration at my lack of accountancy knowledge I put together a crib sheet to help make some more educated selections.
I laminated a copy and kept it to hand so I could take a sneaky peak every now and again - well, it appears that a couple more people had taken a sneaky peak and have also found it more than useful - considering they are accountancy types it struck me that it is more useful than I originally thought.
So, as it's the festive period, and a time for giving; here's your, for accountancy and non-accountancy types alike, very own, laminated Account Type Crib Sheet.
Just add laminate!
PPS Planning Account Type Crib Sheet
Merry Christmas and a Happy New Year !
There are a few performance improvements planned for SP1 and earlier in an interim hotfix. The details I have are high-level but enough to get at least a little excited that development is on going and pertinent to 'in-the-field' issues.
In an upcoming hot fix (KB946222) expected release prior to SP1 is currently being worked on.
When a system contains a large number of assignments, retrieving the list of available assignments for a user has a significant performance issue.
Optimised stored procedure for retrieving assignments to dramatically cut time to retrieve list of available assignments.
Performance issues targeted for SP1 include: Slow performance when re-opening assignment after save/submit. No option to disable what-if calculation on assignment or matrix level which leads to unnecessary what-if queries that slow form performance Successfully submitted change-lists are not automatically from the assignment in the V1 design which leads to unnecessarily large what-if queries MDX query construction optimization Client-Server data volume
These are targeted issues and hence they may not make the cut but it's encouraging all the same.
There is a new hotfix available for Microsoft Office PerformancePoint Server 2007 - The details can be found here:
The hotfix addresses the following issues:
- The property value for a filter does not display the filter selection in a form. Instead, it displays the member label.
This may not sound that important but the change has quite an impact. It seems that initially the PerformancePoint Planning dev team treated member name and member label attributes the same and interchanged them throughout the development. This caused some issues, particularly surrounding filters. Filters always displayed the member label irrespective of what property value was selected. This meant that the label field, for filters, had to be meaningful to the user, whereas ideally the label field is a suitable place for the member surrogate key. Having to make the labels meaningful led to complications around the ETL process and the fact that labels need to be unique.
- You cannot select the members of a Member View that is used in a Microsoft Excel filter.
- The page filter tree is always fully expanded when it is opened. This causes performance issues when large dimensions are used.
Most of the complaints from so far surround performance so it's good to see some action in this area. I have a little more detail on some of the future plans for the performance improvements for planning which I will post about soon.
- If the user has not previewed the Scorecard, the conditional visibility does not work for all languages.
- When you select the "multi-select tree" display method, the Scorecard is displayed incorrectly for a filter. The Scorecard is typically displayed on an incorrect column.
The hotfix is available through Microsoft Customer Support Services.