Troubleshooting Writeable Regions in PerformancePoint Plan

Only certain cells are considered “writeable” in a PPS Plan Excel form. A writeable region is a region where the user can enter data. Here is a checklist of reasons why a region that you expect to be writeable is not.

I put this list together based on some correspondence with the PPS Team, as well as adding in everything I found on the forums… this isn’t my work.  I just wanted to post it somewhere that I wouldn’t always have to go looking for it…

1. Verify your form.

1. Verify that you have authored a form in Excel that uses every dimension/hierarchy that’s in your model (as a column, row, or filter).

2. Verify that the ‘Allow Data Entry’ property is set to true for the matrix.

3. Note that you can only write to cells that match the model’s member set view for time so the form should be authored with the same time hierarchy as the model’s member set view.

4. Verify that the matrix is using the correct model for the cycle.

5. Verify that the matrix is using the correct scenario for the cycle.

6. Check that the cell style “Data Entry Cell – PerformancePoint” has distinct formatting from the cell style “Data Cell – PerformancePoint”, and type directly into a cell expected to be writeable to confirm that the add-in is preventing data entry. (Use the “Reset Default Cell Style” button in the PerformancePoint options dialog to restore default settings for the styles)

7. If you use Custom MDX:

  1. Verify you have crossjoined [Measures].[Value] to the columns.

  2. If you want annotations, you have crossjoined [Measures]. [Model_MeasureGroup_AnnotationCount].

  3. No level that you’re entering data into is aliased with the With Member statement.

2. Verify your cycles.

1. Verify you’ve published the form as a Form Template from Excel.

2. Verify that your form shows up under “Forms” in the “Forms and Reports” section.

3. Verify that the cycle and assignment status is started.

4. Check the Model | Summary page and note down the Current Period; this may affect the time range for the form.

5. Verify the cycle has the correct start and end dates (and that the current date/time is between them).

6. Verify the cycle has the correct scenario.

7. Verify that you’ve assigned the correct form to the Cycle and assigned the correct people as Contributors/Reviewers/Approvers.

8. Verify in Process Management | Cycle Instance | Forms Assignment that the status is started for the user.

3. Verify your security.

1. Verify that user permissions for the roles used in the assignment are set properly. This includes being able to Write data to all leaf nodes, as well as ensuring that the role is turned on for the model.

4. Verify you’re running the form correctly.

1. Verify that you’ve opened the form as a Contributor (i.e. with appropriate credentials), and have opened the Assignment and not just gone to Reports>Open.

2. Verify that you have put all filters to a leaf level.

3. Verify that you are entering in at the correct scenario at a leaf level of all dimensions (unless you have enabled input at all levels, in which case, only the filters must be at leaf levels).

4. Verify that the matrix is showing data at a leaf level for all dimensions in the measure group. Alternately, turn spreading on to see where non-leaf data entry is possible – but note spreading does not work across time.

5. If the writeable region appears for a contributor but not for an approver, check that the option “Allow the approver to edit submissions” was set on the assignment definition. Also be sure that the approver is using the individual assignment (from the review/approve dialog) rather than the grouped assignment.

This entry was posted in Uncategorized. Bookmark the permalink.

Comments are closed.