We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The property "aggregatorName" does not appear to work when using non-editable pivots, i.e. pivot(...). It does however work on pivotUI(...).
See example here: https://jsfiddle.net/vqkk7kh5/2/
In the example if you change pivot(...) to pivotUI(...) you see that the defined aggregator is used.
The text was updated successfully, but these errors were encountered:
This is by design: pivot() and pivotUI() accept different parameters. Please check the documentation.
pivot()
pivotUI()
Sorry, something went wrong.
I had a quick look at the docs here: https://github.com/nicolaskruchten/pivottable/wiki/Parameters
Both Pivot and PivotUI appear to accept "aggregatorName".
Yes but if you read closely they do different things.
On Mar 15, 2016, at 07:07, Jitesh Vassa notifications@github.com wrote: I had a quick look at the docs here: https://github.com/nicolaskruchten/pivottable/wiki/Parameters Both Pivot and PivotUI appear to accept "aggregatorName". — You are receiving this because you commented. Reply to this email directly or view it on GitHub: #456 (comment)
On Mar 15, 2016, at 07:07, Jitesh Vassa notifications@github.com wrote:
— You are receiving this because you commented. Reply to this email directly or view it on GitHub: #456 (comment)
No branches or pull requests
The property "aggregatorName" does not appear to work when using non-editable pivots, i.e. pivot(...). It does however work on pivotUI(...).
See example here: https://jsfiddle.net/vqkk7kh5/2/
In the example if you change pivot(...) to pivotUI(...) you see that the defined aggregator is used.
The text was updated successfully, but these errors were encountered: