| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Change-Id: I2c65709cda6f10810452dfb8aa1a247cb3a5564f
|
|
|
|
| |
Change-Id: Ib15413e73409cc33de01fa92a47b9d1237cfc4b2
|
|
|
|
| |
sorry, huge one...
|
|
|
|
| |
Change-Id: I0fc1fd069440ed6fee378fc2dfd2ed761afbdeab
|
|
|
|
|
|
|
|
|
|
|
|
| |
1) Compare data field name as it is displayed in the table output.
2) In the result tree, store field member names as strings as displayed
in the table output, instead of as ScDPItemData.
GETPIVOTDATA operates on displayed cell values and do textural comparison.
There is no use storing ScDPItemData which screws up value lookup in
the result tree.
Change-Id: I31bc03a6800f4fadf2ba1180d1958354d43e8a07
|
|
|
|
|
|
| |
It *is* a result tree. Let's call it that.
Change-Id: Ie8f3e4c4f6e54fd84d79b80ac98c0be0b0cc42d4
|
|
|
|
| |
Change-Id: I10e0ef90ea7bfd92b46a54dc3d3feff90e50f724
|
|
|
|
| |
Change-Id: I68f4fdab667d86e79225a77964ed90373b391d08
|
|
|
|
| |
Change-Id: I0467cd95e2c6f2f353333b24e1aba737d99e5c20
|
|
|
|
|
|
| |
Looks like I have to put this on the shelf once again...
Change-Id: I6288d019170278e484befaac3ee57cea24a69c0e
|
|
The idea is to avoid parsing the pivot table sheet output in order
to calculate GETPIVOTDATA. The table outout is configurable, and it
will only be more configurable in the future. The gist of my rework
is to calcualte the result of GETPIVOTDATA with the internl result
tree alone.
Also, the same result tree can be used for drill down too, which also
currently parses the table output, therefore subject to the same
limitation & fragility.
Change-Id: Ib0147e2aa2b710dfd627df7f535a685301214a52
|