Peter Eb.

To filter rows and columns by a filter selection has previously been discussed here . But one thing you might not have noticed is that the list of property values (aka the filter scope) is static. If a new member property appears the form needs to be Read More...

(Sorry for the gap since my last post, things have been a bit busy lately in Peter Eb. land…) One simple way to do this filtering is to enable suppress blank rows or suppress blank columns. Then when there is no data (non-null) in the cube for those rows/columns Read More...

For data entry forms (and even some reports) its pretty important to keep contributors focused on their specific task. Its especially easy for users who are not familiar with OLAP or PPS to be confused by some things: "TimeDataView" and "Business Process" Read More...

A common request by form authors is to create a "start here" worksheet page where contributors can change some global filters. Then they advance to other worksheets in the workbook to do their actual data entry. Other times authors just want to link multiple Read More...

Short answer : In SP1 the PPS Planning add-in will use the where clause and life for MDX experts will be back to normal.* Long answer : Because of the extra properties needed for writeback. The CellSet returned by AdoMd.Net does not return member properties Read More...

A recent post by "abdulmohi" in the PPS Planning forums asked about linking or cascading filters. So that once one filter was selected, another filter would be updated to match the first. In abdulmohi's case it was obvious what the linkage should be because Read More...