CMDB Data Foundations Dashboard not displaying metric scores

Larry Youngquis · ‎09-14-2020

In my Paris PDI (with demo data), I installed the new CMDB and CSDM Data Foundations Dashboards. I then ran the scheduled jobs and 11 metric scores were produced.

But the CMDB Dashboard did not display the metric records in the dashboard, as expected.

Inspecting the Metric Score records, the 'Tab' value for the missing records was created with the value of "1.0".

And the CMDB Dashboard widget query is expecting the value of "CMDB Main Tab". Thus, a blank dashboard. The second tab works as expected.

Anyone else experiencing this behavior? I have not tested it beyond my PDI at this point. Wondering what the cause of the erroneous 'Tab' value.

Thanks.

christopher cre · ‎09-14-2020

Hi Larry,

I had the same issue. ServiceNow is creating a problem and will fix it sooner or later.

In the meantime, here is how I fixed it:

Changing the value in the DATA metrics table, won't resolve this issue permanently.

The script that populates the Metrics is actually deleting the scores and re-create them every day.

Therefore, in the script include "CMDBGetWellBase" at the line 87 to 97, you can find the constants the developer teams have created :

_STAGES: { CRAWL: 1, WALK: 2, RUN: 3, FLY: 4 },

_CMDB_TABS : { TAB_ONE: 1, TAB_TWO: 2 },

As you can see the value are INTEGER.

However the value expected by ServiceNow is most of the time a String.

So I changed the those lines of script with:

_STAGES: { CRAWL: "1", WALK: "2", RUN: "3", FLY: "4" },

_CMDB_TABS : { TAB_ONE: "1", TAB_TWO: "2" },

In brief, the script is deleting the metrics and re-creating them every times it runs so the change has to be at the script level or as said Hnin, you could change it at the report level, but it is more difficult to revert multiple reports to the base line compare to changing the script to the base line.

And the actual issue was that the script tried to set a String with an Integer which sometimes result into unexpected results as we have both experienced.

I have tested this fix on my dev, test and production instances and it is working fine.

I hope it can help you, mark the answer as helpful if it did.

Best regards,

View solution in original post

Hnin Haymar · ‎09-14-2020

Hi Larry Youngquist,

We have a fix for this issue coming up in October release of the dashboard scoped app.

We only discovered this issue on some instances, and it did not show up in any of the instances we tested with.

The underlying cause is the data type of the "Tab" column's datatype; it was a "choice" type. When we changed this type to "Integer" type, the issue is solved. We're introducing a new column to fix this issue in October and the reports will be referencing the new column.

For now, as a workaround, I'd recommend changing the filter condition of the CMDB Foundations Indicators to "Tab" is NOT "Additional CMDB Areas". This will solve the empty report issue. However, please note that this action is considered a customization and will cause the files to be skipped during upgrade time, and an administrator would need to manually overwrite the customization with the upgraded file.

christopher cre · ‎09-14-2020