View Calculated Field not in Field List of same view.

Laura Corbet shared this question 3 months ago
Answered

I created a calculated field in a view. I then wanted to use that calculated field in a second calculated field in the same view but the first calculated field is not available in the drop down.


As a work around, I am using virtual tables to freehand SQL the calculation and then reference the output in calculated field, but doesn't seem efficient.

In reports, I AM able to reference calculated fields in new calculated fields, just not in the view. Is this the way the system functions?

Comments (1)

photo
1

Hi Laura,


Thanks for your question.


That is correct, Calculated Fields can only be used in Calculated Fields when they are defined in the View, and used in a Report. Is there not a way that you can create a Virtual Table with all the calculations that you need at the View level? You may also be able to utilise Advanced Functions in the Report. If you give me a little more information about the Calculation I may be able to provide further guidance.


Kind regards,

Simon

photo
1

Thank you Simon.

photo
1

So I have a date time field in the database. I used the Date Function to get the 24hour time in Hour format. That Date Function field is not available in the Calculated Field dialog box in either the View OR the Report. This doesn't seem correct to me. Shouldn't I be able to use it in a calculated field?

photo
1

If I use the same date time field in the database and use calculated field using pre-defined functions and select SQL Hour, the resulting calculated field is then available to me in both the View and The Report for other calculations.

Not sure what the logic is in the system: why are some calculated fields available to be used in subsequent calculated fields, but others are not? (having the type metric/dimension be the same)

photo
1

Hi Laura,


Would you be able to provide some screenshots to help explain the Date/ Functions you are attempting to apply?


If your original message regarding Calculated Fields is specifically about Date/ Time functions, it might be worth taking a step back. Date/ Time are handled in a slightly different way in Yellowfin compared to other Calculated Field types, and you might be able to get the results that you are trying to achieve in a much simpler way. For example, Date/ Time data can be shown to each user based on their individual timezone without any additional data manipulation to the original data. This is done through formatting the original data, rather than changing it - which is why you might be having issues using it in a second Calculated Field.


If you help me to understand the re-calculations that you needed to apply in the first place, I should be able to provide you with clearer guidance.


Kind regards,

Simon

photo
1

Hi Laura,


I just wanted to check in to see how you are traveling with this issue. If you could provide a little more information about the Date Functions you are attempting on applying, I might be able to provide you with an alternate solution.


Otherwise, if this is no longer an issue, feel free to let me know and I will go ahead and mark this question as closed.


Kind regards,

Simon

photo
1

Hi Laura,


I'm just messaging to let you know that I am marking this as closed due to inactivity.


If this is still something that you require assistance with, please respond here and I will get back to you shortly.


Kind regards,

Simon

photo