AS OLAP. Why is there no data in the middle of the pivot table?

Question

excel

Cuba has a partition for 2010 created by the query: select Date, summ, idPoint from Products where Year(Date)=2010.
The data is broken down by Date and Sale Point (idPoint ). After recalculating the data in the Excel pivot table, I get a picture:
in terms of dates, the data is from the 1st to the 10th, then a gap, then from the 20th to the 31st. Moreover, there is data for one Point of Sale for each day, and for the rest, part of the data is not displayed. Schematically, the problem looks like this:
Dates | 1 2 3 4 5 6 7 8 9 10 11 12 13 14
------------------------------------ --------------------
Point_1| 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
Point_2| 2 2 2 2 2 p p p p p p p 2 2 2 2 2
Point_3| 3 3 3 3 3 p p p p p p p 3 3 3 3 3 The
letter "p" denotes an empty value.
The query that creates the partition returns data for all days of the month for all Points of Sale.
The cube stores partitions by years from 2008 to 2015. Only the partition for 2010 was recalculated. For the current 2015, the partition is recalculated daily.
What could be the problem?

Answer 1

He asked himself - he answered.
The curved data was taken from the OLAP database (read the cube) - the data was indeed calculated incorrectly there, which was shown by the MDX query in Management Studio. Why did I think the data in the cube was correct!? because he did the processing of a partition from a cube project in Business Intelligence Development Studio (read MS Visual Studio). There, the porting is processed, and a report with normal data is built in the cube browser (Browser). But the recalculated data does not get into the database itself! Most likely, in the processing dialog, you need to check the box: Change Settings --> Process Affected Objects - then the data should be registered on the server after the calculation (did not check, but I think it is).
I solved the problem this way: I processed the partition directly in Management Studio. The data was calculated and began to be displayed normally both in the MDX query and in Excel.
Conclusion: without the "Process Affected Objects" checkbox in Visual Studio, processing occurs, but the data does not get into the cube database. but remain somewhere on the local machine from which they did the recalculation.