We have BOXI R2 on Windows. We have MHF1. I have a very straight and simple universe with only one table (and it’s NOT a derived table or a view).
I have 2 measure objects with the where clause for creating metrics. I have copied the where clause and also made sure that the syntax is fine.
Anyways here is the where clause if someone would like to take a look.
(ASHAH.TAGG.AGGDATE between @Prompt('BEGIN_DATE','D',,mono,free) AND
@Prompt('END_DATE','D',,mono,free))
I imported the universe and created a metric, until then everything worked fine. But when I try to refresh my metric I get this error
.
Please look at the attached screenshot.
I even checked the CI_PROBE table and the table does not have any details on this metric refresh. I don’t think the query is even going to the database. I tried creating my own calendar instead of using the default BO daily calendear and that does not work either.
I looked at all the metric related posts on the forum, but could not find any that has the same issue as I do. I will appreciate your reply.
PM is the most half-baked enterprise application I’ve ever used, since an in-depth knowledge of the inner workings of the application stack is a prerequisite to debugging even simple problems like this.
That said, ci_probe is one of the PM repository tables. You can query it directly with SQL, or use one of the pre-built Metrics universes.
Within that table, probe_name and probe_code can be used to find the metric in question. Once you identify the row, check the executable_sql column. This is supposed to hold the actual SQL that is used to refresh the metric.