Calculated field in Sub-query

Asaf Hanina shared this idea 9 months ago
Idea Logged

Hey,

We have issue by using calculated field over and over again while we are using subquery in a report

For example:

If I create a calculated field in the subquery and  want to use it in the main query.. I can’t

thanks

Assaf Hanina

TFM - Data Analyst

This message has been scanned for malware by Websense. www.websense.com

Comments (7)

photo
0

Hi Asaf,

Thanks for reaching out to support with your issue.

Just wanted to make sure I understand your situation:

You have a calculated field in a report subquery -


b4f2959d50ca88ecbab3b201f5c36aa5


The goal would be to use this calculated field in your main query, but the field you have created is not present here -


d43588ee4432f31ce4c9ab781098b333

Is that correctly detailing your experiences in this case?

Thanks,

Eric

photo
0

Yes, my point is that when using subquery u can not use calculated field more than once

From: Support Queue <support@Yellowfin.bi>

Sent: Tuesday, March 19, 2019 8:49 PM

To: Asaf Hanina <asafha@tfm.ltd>

Subject: Re: Calculated field in Sub-query [#12907]

photo
0

Hi Asaf,

Just to confirm, I tested creating and adding multiple calculated fields from within my subquery, this worked as expected.

463bd61c491d05e00afd0921c8b722afHowever, these calculated fields did not show up in the list for my master query, or any additional subqueries I created afterwards.

To clarify your reply, your "point is that when using subquery u can not use calculated field in other queries?"

Thanks,

Eric

photo
0

Hey Eric,

yes

From: Support Queue <support@Yellowfin.bi>

Sent: Wednesday, March 20, 2019 7:34 PM

To: Asaf Hanina <asafha@tfm.ltd>

Subject: Re: Calculated field in Sub-query [#12907]

photo
0

Thanks for confirming, Asaf. I wanted to make my report succinct for developers.

One possible alternative "fix" for this behavior: I did find a way to get a calculated field to show up throughout all my report queries. This was done by adding the calculated field at the View level, which makes the calculation a metric that is usable in both the master and sub query:


bb207a450f7384cb33a2fea175997d9d

05e08606585be212df3c170ff8952ac3

Would this be a possible solution in your environment? Also, could you confirm for me that you'd like to create a developer task to address the issue as we've identified here?

photo
0

I already using this solution, but it’s not cover 100% of the cases

From: Support Queue <support@Yellowfin.bi>

Sent: Thursday, March 21, 2019 5:49 PM

To: Asaf Hanina <asafha@tfm.ltd>

Subject: Re: Calculated field in Sub-query [#12907]

photo
1

Hi Asaf,

I've gone ahead and created an enhancement request with our developers for this added functionality. Updates to the task will be provided here as they are available. I've in turn marked this ticket as Idea Logged; feel welcome to reply to this thread with related inquiries.

Thanks,

Eric