Data different than an aggregation in the crosstab intersection
Answered
Morning,
Is there any way to have a value different than an aggregation in the intersection between a column and a row within a crosstab? For instance, a label or a date (always a unique value).
Many thanks!
Best Regards,
Joan.
Hi Joan,
Thanks for reaching out. I am a bit confused as to what exactly you are seeking here. Would you mind elaborating with an example screenshot?
Thanks,
Nathan
Hi Joan,
Thanks for reaching out. I am a bit confused as to what exactly you are seeking here. Would you mind elaborating with an example screenshot?
Thanks,
Nathan
Hi Nathan,
I'm sorry for the delay, please find three examples in the attached excel file. The first one is the only one we were able to create but we would also like to create crosstab like examples 2 and 3.
Many thanks.
Best Regards,
Joan.
Hi Nathan,
I'm sorry for the delay, please find three examples in the attached excel file. The first one is the only one we were able to create but we would also like to create crosstab like examples 2 and 3.
Many thanks.
Best Regards,
Joan.
Hi Joan,
Thank you for the clarification. Unfortunately, as the cross-tab error shows, the underlying SQL requires you to have "one Column dimension, one Row dimension, and one aggregated metric field". In this case there is no way to get around having to aggregate a metric. And while it is possible to make text or dates a metric, aggregating them with count does not suit your needs.
I believe that the best way to accomplish this will be through the use of append sub-queries. Using your 'Booking Level' data as an example:
Create a sub-query for each year, placing level into columns, and filtering by that year. You can then re-name the columns to reflect the filtered year, producing a graph that looks very similar to your desired result.
Here Is how I have the filters set up:
I apologize for the inconvenience and please let me know if this solution meets your needs.
Regards,
Nathan
Hi Joan,
Thank you for the clarification. Unfortunately, as the cross-tab error shows, the underlying SQL requires you to have "one Column dimension, one Row dimension, and one aggregated metric field". In this case there is no way to get around having to aggregate a metric. And while it is possible to make text or dates a metric, aggregating them with count does not suit your needs.
I believe that the best way to accomplish this will be through the use of append sub-queries. Using your 'Booking Level' data as an example:
Create a sub-query for each year, placing level into columns, and filtering by that year. You can then re-name the columns to reflect the filtered year, producing a graph that looks very similar to your desired result.
Here Is how I have the filters set up:
I apologize for the inconvenience and please let me know if this solution meets your needs.
Regards,
Nathan
Hi Nathan,
Many thanks for your help, we will keep your proposal in mind in order to solve that kind of situation.
Best Regards,
Joan.
Hi Nathan,
Many thanks for your help, we will keep your proposal in mind in order to solve that kind of situation.
Best Regards,
Joan.
Hi Joan,
I was just wondering if you have had any luck in resolving this issue? Please let me know if you have any additional questions, or if you would be okay with me closing this ticket.
Regards,
Nathan
Hi Joan,
I was just wondering if you have had any luck in resolving this issue? Please let me know if you have any additional questions, or if you would be okay with me closing this ticket.
Regards,
Nathan
Hi Nathan,
Yes, we did. We were able to get the report with your proposal, you can close the ticket.
Many thanks for your help.
Best Regards,
Joan.
Hi Nathan,
Yes, we did. We were able to get the report with your proposal, you can close the ticket.
Many thanks for your help.
Best Regards,
Joan.
Hi Joan,
Glad to hear you got both tickets resolved! I have closed them, but please don't hesitate to reach out if you have any additional questions or concerns!
Regards,
Nathan
Hi Joan,
Glad to hear you got both tickets resolved! I have closed them, but please don't hesitate to reach out if you have any additional questions or concerns!
Regards,
Nathan
Replies have been locked on this page!