Forum Discussion
Needle in a Haystack?
Hi, i inherited an import pi report with an auxiliary like table called Measure_Metrics. That table has over 100 calculations in it like Sales-MTD. When i hover over the table, rather than a refresh date i see "Invalid Date". There are no records in it in the desktop environment. Would finding what causes the "invalid date" error in a table with over 100 calcs be like finding a needle in a haystack? Or is there a way to better pinpoint which calc(s) is/are causing the problem? Our eyes were drawn to the issue when a number of kpis started showing double dashes rather than actual values.
4 Replies
i should have pointed out that in the ws we see no error symbol suggesting the daily refresh failed. and i'm trying a refresh on the desktop and watching the refresh list of tables to see if i'll have an opportunity to see the error and more detail related to the error. So far i see Schema synchronized which i think means the tables it depends on are refreshed. Also, when i click edit query i see the source shown below which at the moment means nothing to me. There are 2 applied steps called change type and remove columns.
the refresh on the desktop finished without giving me an opportunity to see a failed status on this table.
= Table.FromRows(Json.Document(Binary.Decompress(Binary.FromText("i44FAA==", BinaryEncoding.Base64), Compression.Deflate)), let _t = ((type nullable text) meta [Serialized.Text = true]) in type table [Column1 = _t])
one other thing im noticing is that this calc in dimdate is always returning NO. And this report depends on MTD flags in a variety of places including where month is designated as current month type CM.
MTD = IF(DAY(now()-6/24) <= (DimDate[DayNumberOfMonth]), "No","Yes")
when i replaced -6/24 with -(6/24) the issue persisted. When i removed -6/24 altogether the report started working. I still see an empty auxiliary table and i still see "invalid date" when i hover over its name. I' guessing right now that "invalid date" applies to one calc that maybe doesnt matter? And that 0 rows showing for the auxiliary on the desktop is ok , maybe?
Can the community clarify why my change made a difference and why the weird behavior surrounding the auxiliary table continues. As far as i can tell, calcs in the auxiliary source the kpis that were broken but that suddenly started working on the desktop. im waiting to publish until i see some of the responses here. According to my peers this has been working for weeks. And suddenly broke yesterday.
