I know the beta 'nested IN' functionality has only been tested in a (regular) Table macro.
I've also gotten it to work fine in a Value Query, as would be expected.
However, I'm getting an error when trying to implement in a Pivot Table: Error in pivot-table macro: undefined method `accept' for nil:NilClass
Any suggestions? Anyone able to get 'nested IN' functionality to work in a Pivot Table?
Here's my Table Query (which works):
table query: SELECT number, name, 'Task Status', Team, 'Iteration - Scheduled', 'Estimate', 'Story Tree - Story' WHERE Type = Task AND 'Story Tree - Project' = NUMBER 2732 AND 'Story Tree - Story' IN (SELECT number WHERE type = Story AND Release = 74)
Here's my Value Query (which works):
value query: SELECT SUM(Estimate) WHERE type = 'Task' AND 'Estimate' != 0 AND 'Estimate' != NULL AND 'Task Status' = 'Not Started' AND 'Story Tree - Story' IN (SELECT number WHERE type = Story AND Release = 74)
Here's my Pivot Table, which throws the error:
pivot-table columns: 'Task Status' rows: 'Team' conditions: type = 'Task' AND 'Estimate' != 0 AND 'Estimate' != NULL AND 'Story Tree - Story' IN (SELECT number WHERE type = Story AND Release = 74) aggregation: SUM(Estimate) totals: true empty-columns: false empty-rows: false
Notes: Task Cards are below Story Cards. 'Release' is a Story Card property. 'Story Tree - Story' denotes a Story Card on the Story Tree (yes, I know that's ugly). All other card properties mentioned are Task Card properties.
I could really use this Pivot Table. If using 'nested IN' doesn't work, it appears I'm stuck using ~18 Value Queries, which I'm not looking forward to.
Comments
1 comment
Hi Sam,
Thanks for the helpful example. You're right that the structure of the original table suggests that you should be able to create a pivot table from that data. Unfortunately, it does appear that pivot tables don't work with nested IN. I have added this to our backlog. Sorry about the 18 value queries.
Thanks,
Jay
Please sign in to leave a comment.