All: We appreciate the votes and comments on this idea. As @bgeorge-eng
has noted, "Undo" is available in Analysis Workspace. Hopefully you have
all had a chance to get your feet wet with Workspace. We believe
strongly that it is the future of analysis on the web, and will be
investing heavily in adding more functionality there. Consequently, we
won't be adding Undo in Reports & Analytics or Ad Hoc Analysis.
converted the user's time zone into the report suite time zone, but I
could be wrong about that. I don't see the "user's clock could be off"
as a statistically significant problem; the overwhelming majority of
people are likely ot be accurate within a few minutes, no? Either way, I
don't think any of this takes away from the merit of this idea, which
has been commonly requested and up-voted.
Hi @GilliganOnData2, I think we already do this. We don't show it
directly over the data point, but it is in the legend. See screen shot:
Is there something I am missing here? Is the lesson just that users may
not think to look over there, so it should be closer to the data point
Thanks for the feedback, @GilliganOnData2. I don't know that we've
discussed fonts per se, but we have definitely talked about giving you
more control over things like color pallettes so that you can draw
attention to certain data. Great suggestion to add to that list.
With all due respect, @jaydge88, things that seem easy from the outside
often are not as simple as they appear. The biggest challenge with this
request is that we do not force your project layout to respect
traditional page boundaries. We have heard from many users that you do
not want visualizations to break between pages (e.g., top of a bar graph
on one page, bottom of the same bar graph on the next page), which means
we would need to enforce page breaks—something that we don't do today.
Noted, @michael-jet, and thanks for the reminder. This is a good idea,
and we will keep an eye on it. The workaround that you noted is still
relevant, and if you or anyone else has this use case, we recommend
passing hour of day into a prop or eVar so that it aggregates across
days at the hour level for now.
These are all great points. Some thoughts: 1. For comparing hours of day
across days, there's currently a bug (or perhaps bad design) related to
the existence of the date in the rows when showing hour (as you pointed
out). The result is that you can't really compare a single hour across
days. That should be fixed in an upcoming release. 2. Good point about
25 items in a graph. I'll send this over to our engineering team to
review and hopefully get that increased. 3. This might be coming soon.
@jer @viclin: This should be available on November 10. Note that this
will NOT give you hour as a dimension to be used anywhere. It will let
you compare a specific hour against the same hour on another day. For
hour as a dimensions, we continue to recommend a Time Parting solution
In case you haven't been doing this, when you add that text
visualization you can collapse it so that it only shows its title. I
know it's not a "solution" to this need, but as a workaround it is not