Fixed case of expression in OOTB report. #17191
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This was causing an issue when copying this report and trying to change an expression of new report.
Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1558087
@gtanzillo please review/verify.
was getting error prior to fix:
Error building timeline PG::UndefinedTable: ERROR: missing FROM-clause entry for table "miq_sets" LINE 1: ...s"."ems_id" AS t0_r15 FROM "policy_events" WHERE ("miq_sets"... ^ : SELECT "policy_events"."id" AS t0_r0, "policy_events"."miq_event_definition_id" AS t0_r1, "policy_events"."event_type" AS t0_r2, "policy_events"."miq_event_definition_description" AS t0_r3, "policy_events"."miq_policy_id" AS t0_r4, "policy_events"."miq_policy_description" AS t0_r5, "policy_events"."result" AS t0_r6, "policy_events"."timestamp" AS t0_r7, "policy_events"."target_id" AS t0_r8, "policy_events"."target_class" AS t0_r9, "policy_events"."target_name" AS t0_r10, "policy_events"."chain_id" AS t0_r11, "policy_events"."username" AS t0_r12, "policy_events"."host_id" AS t0_r13, "policy_events"."ems_cluster_id" AS t0_r14, "policy_events"."ems_id" AS t0_r15 FROM "policy_events" WHERE ("miq_sets"."created_on" BETWEEN '2018-03-19 00:00:00' AND '2018-03-25 23:59:59.999999')
after fix: