Editting report removes conditional formatting from calculated field
Defect Fixed
When editing or copying a report, conditional formatting is removed from columns that are also calculated fields. We are on 7.3+ build 20180409.
This seems like it was supposed to be fixed in 7.3 - 20170523: 653 - Fixed issue with conditional formatting disappearing when user edits a report
Is the calculated field an added twist that needs to be corrected?
Hi Robert,
Thanks for reaching out. I don't think this is related to using Calculated Fields. Xavier Ona, also at Credible, logged this as well the other day. I mentioned that the issue that persists comes down to reports that are built using Sub-Qeuries, and also only occurs in 7.3, but all works as expected in 7.4.
Can you confirm whether the report you're using also contains Sub-Queries? This way I can link this also to that existing defect.
Thanks,
Mike
Hi Robert,
Thanks for reaching out. I don't think this is related to using Calculated Fields. Xavier Ona, also at Credible, logged this as well the other day. I mentioned that the issue that persists comes down to reports that are built using Sub-Qeuries, and also only occurs in 7.3, but all works as expected in 7.4.
Can you confirm whether the report you're using also contains Sub-Queries? This way I can link this also to that existing defect.
Thanks,
Mike
Hi Mike,
Any update on this DEFECT ?
Kind Regards,
Asif Bhat
Hi Mike,
Any update on this DEFECT ?
Kind Regards,
Asif Bhat
Hi Asif,
There's no update on this as of yet. As a reminder, this issue does not occur in 7.4. I've requested an update on this case.
Regards,
Mike
Hi Asif,
There's no update on this as of yet. As a reminder, this issue does not occur in 7.4. I've requested an update on this case.
Regards,
Mike
Hi Robert,
Just writing to let you know this has been fixed and will be included in the next build of 7.3. I'm trying to obtain an ETA for said build.
Alternately, if you can make your way to 7.4, it's included in the latest build of that, which is 7.4.10.
Regards,
Mike
Hi Robert,
Just writing to let you know this has been fixed and will be included in the next build of 7.3. I'm trying to obtain an ETA for said build.
Alternately, if you can make your way to 7.4, it's included in the latest build of that, which is 7.4.10.
Regards,
Mike
Replies have been locked on this page!