Drill-through/Output data from Pivot table entry: "pivot filtering" about pivottable HOT 9 CLOSED

This is a great idea. I see two ways of doing it, both of which leverage the jQuery data() system.

One option would be for the Table renderer to attach to each td element a filtering function, which you could use to iterate over the data-set to figure out which records match the cell. This may use less memory but be slower.

Another option would be the same idea except that we would attach an array of records to each td. This may use more memory but be faster.

In either case, you could attach a click handler which could access the matching records and display them however made sense. What do you think?

from pivottable.

For the second approach, is it not sufficient to just attach the indices of the records in a given pivot table entry? Then on click, the desired records are accessed and output.

from pivottable.

1- Is there any documentation that shows what the code should look like in a Sharepoint Content Editor Web Part?
That web part is expecting html,js,css or all. There appears a number of code modules but it was not clear what piece of code brings them altogether to display the pivot.
2- What mechanism can be used to refresh the connection to the CSV file?
Thanks

from pivottable.

Hi,

1. I don't really know much about Sharepoint so I won't really be able to help you with that, sorry...

2. There is no real connection to a CSV file to refresh... The input formats are documented here: https://github.com/nicolaskruchten/pivottable/wiki/Input-Formats

from pivottable.

Pull request #141 (which won't be merged) shows how someone patched this library for this purpose

from pivottable.

@samuelleach that second approach you just mentioned is actually really just the 1st option suggested by @nicolaskruchten. Unless you were to sort your data set and use a searching algorithm (binary search is probably the only feasible algorithm if ID's are used), i doubt there would be any convenience or performance increases in using the indexes(Id's is the way you would probably use it) as opposed to the records themselves

from pivottable.

@nicolaskruchten is there a plan to add a callback, so that one wouldn't have to patch the renderer to get access to the records underneath the aggregates?

from pivottable.

I'm looking at merging #557 or something like it.

from pivottable.

functionality for this is now in master!

from pivottable.