Forum Discussion
On calculated field, using the date hierarchy causes an error.
- 10 years ago
It is funny - some observations ... was able to show the the hierarchy for calucated date after doig the following 2 actions.
a) Set the calculated date field to Date/Time
b) saved the pbix file.
then used the calcualted field in a visual....
I'm on Version: 2.34.4372.322 64-bit (April, 2016)
Hierarchy showing up for Date3Logic for the Calculated Date Field
Never mind, Just tried it - not working with FORMAT either
Thanks for trying, sornavoor! It almost feels like it is getting caught in some type of circular reference, though not sure why, nor if that makes sense. But when the formatting matches and types match, I can't guess what would make it fail!
- sornavoor10 years ago
Resolver I
It is funny - some observations ... was able to show the the hierarchy for calucated date after doig the following 2 actions.
a) Set the calculated date field to Date/Time
b) saved the pbix file.
then used the calcualted field in a visual....
I'm on Version: 2.34.4372.322 64-bit (April, 2016)
Hierarchy showing up for Date3Logic for the Calculated Date Field
- Anonymous10 years agoNot applicable
Thanks, sornavoor! Oddly, I started by changing the format, but adding the calculated date to a new visual did nothing. And then when I added in the format function around my if statement, I got an error. It was not until I deleted the format function and forced a recalculation that the visual started showing the proper date hierarchy! Strange, but thanks so much for your help!
Scott
- ericleigh0079 years ago
Advocate II
Yes, this is definitely a bug.
If this happens, you have to toggle the formst back and forth.
I toggled back to date, and then back to date/time for my field, and that caused the hierarchy to show up.
Would be great if the team could fix that one. Took me a whliei to find the answer and then mess around a bit before i was able to work around it.