Column metric aggregated in cross tab
19 March, 2014
Hi,
We have a cross tab report in which we are using year number(metric) as the column with other dimensions and other metrics aggregated.By default the year number gets aggregated and we are not able to remove this.Since its a year number we do not want this to be aggregated and this year number is in turn used in other fields for calculations.
This issue was not there in the 6.3 version and we do have few reports designed this way.Now after YF7(jan build) upgrade these reports break while editing .
Thanks,
Renison
We have a cross tab report in which we are using year number(metric) as the column with other dimensions and other metrics aggregated.By default the year number gets aggregated and we are not able to remove this.Since its a year number we do not want this to be aggregated and this year number is in turn used in other fields for calculations.
This issue was not there in the 6.3 version and we do have few reports designed this way.Now after YF7(jan build) upgrade these reports break while editing .
Thanks,
Renison
Hi Renison,
Because YF7 no longer has 3 separate sections for Rows,Columns, and Metrics, all metrics are aggregated.
Because your Year field is saved as a Metric it is automatically aggregated.
Add an addition Year column into your available fields at View level and save it as a Dimension, leave the current Year field as a Dimension so that your calculations will continue to work.
Then instead of using Year (Metric), use the Year(Dimension) in your CrossTab reports.
Regards,
Stephen
Because YF7 no longer has 3 separate sections for Rows,Columns, and Metrics, all metrics are aggregated.
Because your Year field is saved as a Metric it is automatically aggregated.
Add an addition Year column into your available fields at View level and save it as a Dimension, leave the current Year field as a Dimension so that your calculations will continue to work.
Then instead of using Year (Metric), use the Year(Dimension) in your CrossTab reports.
Regards,
Stephen
Hi Stephen,
Thank you so much for your reply.I understand that we could treat it as dimension and we have already tried this.The need of metric field is that it is used for a calculated fields and then used in cross tab.This calculation is report specific.If we treat it as dimension and use it for calculated fields it would again treat it as metric.
In the row if i drop a metric field it gives an option to remove the default aggregation in advance functions.But why doesn't same thing work for metric field in column? and i know my cross tab report has already a metric field with aggregation which is required.
Regards
Renison
Thank you so much for your reply.I understand that we could treat it as dimension and we have already tried this.The need of metric field is that it is used for a calculated fields and then used in cross tab.This calculation is report specific.If we treat it as dimension and use it for calculated fields it would again treat it as metric.
In the row if i drop a metric field it gives an option to remove the default aggregation in advance functions.But why doesn't same thing work for metric field in column? and i know my cross tab report has already a metric field with aggregation which is required.
Regards
Renison
Hi Renison,
There is an existing dev task (TASK # 159626) which relates to YF v7 not allowing the use of a Metric as a Row/Column in a Cross Tab Report.
The solution i provided is a work around until this gets implemented.
You will now have 2 Year columns :
- 1 as a metric used in your calculations, and
- 1 as a dimension to be used for your Cross tab Reports
Hope this explains what I was trying to show you previously.
Regards,
Stephen
There is an existing dev task (TASK # 159626) which relates to YF v7 not allowing the use of a Metric as a Row/Column in a Cross Tab Report.
The solution i provided is a work around until this gets implemented.
You will now have 2 Year columns :
- 1 as a metric used in your calculations, and
- 1 as a dimension to be used for your Cross tab Reports
Hope this explains what I was trying to show you previously.
Regards,
Stephen
Hi Stephen,
Can you please provide the ETA for this Task ID 159626 ? as it helps us decide on our yf upgrade process
Thanks,
Renison
Can you please provide the ETA for this Task ID 159626 ? as it helps us decide on our yf upgrade process
Thanks,
Renison
Hi Renison,
That task (159626) has been scheduled for the May 7.0 & 7.1 release.
Sorry for the inconvenience, and please let us know if there was anything else you were after.
Regards,
David
That task (159626) has been scheduled for the May 7.0 & 7.1 release.
Sorry for the inconvenience, and please let us know if there was anything else you were after.
Regards,
David