We are using Microsoft Performance Point Server against a SQL Server Analysis Cube.  We are finding that when a new location is brought on that we are forced to rebuild any reports that are using the location dimension.  It knows that it's updating somehow because all of the values zero out.  Once we remove and re-add the locations dimension on the report, the values come back to the screen.  I somewhat understand why it's doing this but would hope that if we added a new location that the system would be smart enough to decifer the new location information and calculate the new rows?  Or am I wrong in my assumption and we have to manually reconfigure each report that utilizes this dimension anytime the dimension adds a new location?  Hopefully this makes some sense. Have you seen this behaviour yet?

Sorry for not returning the reply, that is exactly what was happening.  We were manually selecting the members instead of using an MDX Statement to pull the members for the listing.  It took some time to figure out the proper MDX statements but eventually we got it to work the way we needed it to.  Thanks for the posted reply.