You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, it seems like the logic for doing any of the time based calculations for MTD, QTD, or YTD, relay on a hidden measure called "_ShowValuesForDates". That makes sense in order to limit the dates that are using the in the formulas. However, it seems like the logic for that hidden measure is flawed, or at least I don't understand the correct way to use it. It seems that it always returns true, no matter what the date, since the "__FirstDateVisible" is always less than the last date with data. I was able to work around this by adding another calculated column to the dates table that only returns true if that row's date is less than the max date in my data table and then adding that column as a filter on my page, but it seems like that should be built into the generated dates table somehow. If there is another way I should be using this, please let me know.
The text was updated successfully, but these errors were encountered:
The measure _ShowValuesForDates is created dynamically based on the Date columns selected in Bravo to generate the Date table. If you set a fixed range of years, that probably doesn't work automatically, and you should adjust that manually. Can you provide the _ShowValuesForDates definition you have in the model so we can validate whether this is your case?
Hello, it seems like the logic for doing any of the time based calculations for MTD, QTD, or YTD, relay on a hidden measure called "_ShowValuesForDates". That makes sense in order to limit the dates that are using the in the formulas. However, it seems like the logic for that hidden measure is flawed, or at least I don't understand the correct way to use it. It seems that it always returns true, no matter what the date, since the "__FirstDateVisible" is always less than the last date with data. I was able to work around this by adding another calculated column to the dates table that only returns true if that row's date is less than the max date in my data table and then adding that column as a filter on my page, but it seems like that should be built into the generated dates table somehow. If there is another way I should be using this, please let me know.
The text was updated successfully, but these errors were encountered: