Calculated field and dependent fields

Q&A
, ,
1

Does calculated field require all the fields used in its calculation to be present in the visual?

For ex:
End-to-End delay =
avgOver({Audio Tx Path Delay (ms)}, [{label}, {iter}], PRE_AGG) + avgOver({Audio Rx Path Delay (ms)}, [{label}, {iter}], PRE_AGG) + avgOver({Average Audio RTP to RTP Delay (ms) (MO to MT)}, [{label}, {iter}], PRE_AGG) + avgOver({Avg Audio De-jitter Buffer Frame Delay during talk (ms)}, [{label}, {iter}], PRE_AGG)

where {Audio Tx Path Delay (ms)}, {Audio Rx Path Delay (ms)}, ({Average Audio RTP to RTP Delay (ms) (MO to MT)} … are calculated fields as well

If they are omitted in the visual, the End-to-End delay calculated field shows null.

2

PRE_AGG’s shouldn’t need them to be referenced.

If you include them in the visual you’re saying that the column shows data?

3

Hi @Max
Yeah, if I include them in the table then the End-to-End delay calculated field shows the corresponding value and if they aren’t included in the table then it shows NULL which is not expected

To explain my problem even better -

If my pivot table has all the calculated fields then E2E Delay has a value -

Audio Tx Path Delay 5
Audio Rx Path Delay 4
Average Audio RTP to RTP Delay (ms) (MO to MT) 6
Avg Audio De-jitter Buffer Frame Delay during talk (ms) 2
End-to-End Delay 17

And if they aren’t in the table -

End-to-End Delay null

4

Hello @tpanati !

I am going to archive this topic since it has been open for an extended period of time. If you would still like assistance with this, or if you have a new Quick Sight question, feel free to post a new topic in the community so you will be at the top of the priority list for a response from one of our Quick Sight experts. Thank you!