Forum Discussion
How to retrieve js Date from a date column in DataViewTable
Your hierarchy isn't visible in your screenshot's fields pane, but at a guess, your hierarchy in the visual contains levels for Year, Quarter and Month, but not the actual date?
If so, you would need to ensure that this is included. If you're using auto date/time, then you could change the hierarchy to use the underlying date column instead in the visual.
If your supplied column is a date/time, according to the data model, then your type will flag accordingly, e.g.:
Do you get the same output in a table visual? I've set up a similar hierarchy and this is what I get (which is what I'd expect):
If you add and actual Date column to your hierarchy then the column and type should be visible, e.g.:.
This is always a good test if you're using the table data view mapping - it it doesn't look right here, it won't look right in your visual's data view.
Also, you can't guarantee that your end users will be using a date hierarchy; most will put in a raw date. I'm not sure if this is an important requirement for your visual but you will need to ensure to specify this in any documentation for your end users if so.
Daniel
dm-p would you mind shedding some light on this issue?
Super UserYour hierarchy isn't visible in your screenshot's fields pane, but at a guess, your hierarchy in the visual contains levels for Year, Quarter and Month, but not the actual date?
If so, you would need to ensure that this is included. If you're using auto date/time, then you could change the hierarchy to use the underlying date column instead in the visual.
If your supplied column is a date/time, according to the data model, then your type will flag accordingly, e.g.:
Do you get the same output in a table visual? I've set up a similar hierarchy and this is what I get (which is what I'd expect):
If you add and actual Date column to your hierarchy then the column and type should be visible, e.g.:.
This is always a good test if you're using the table data view mapping - it it doesn't look right here, it won't look right in your visual's data view.
Also, you can't guarantee that your end users will be using a date hierarchy; most will put in a raw date. I'm not sure if this is an important requirement for your visual but you will need to ensure to specify this in any documentation for your end users if so.
Daniel
Hi dm-p ,
Thank you very much for the response, the solution serves us to get the date object !
Thanks a lot dm-p!
It seems then like we're faced with a trade-off: either use the date hierarchy and its automatic aggregations but lose the type info and actual dates or use the underlying date column but get only the lowest level of the hierarchy... Is there any way to get both? like, know from a hierarchy column that it is the result of organizing in a hierarchy what was originally a date column and get the actual date?- dm-p
As date hierarchies can be entirely contextual to a data model (if used at all), there's no generic solution to this. If your visual needs specific portions of a date to support a hierachy, you are best guiding the user to add the columns that the visual requires for the correct level of grain in the data view, so that they can create them in their model if they are not present and then add them to the visual.
The only way I'm aware of to get everything would require some knowledge from the end-user to make the dataset work how you intend. One of the following would be possible:- Ensure user adds all columns from the hierarchy rather than the hierarchy itself, so that each distinct column is present in the data view for the data role. If you specifically need all parts, then I would suggest creating data roles for each part of the hierarchy you require to make sure that the user supplies them all.
- Add drill-down support for the data role and ensure the user has expanded the visual all the way down to the lowest level.
Either one of these would change the grain of the data view to the lowest possible level so you would need to aggregate them yourself in your ViewModel (but I guess you might already be doing that). You may also need to work out how to resolve the data view for your visual if the user doesn't supply what you intend, so that they can be guided accordingly.