Let's say I have 3 mutually exclusive segments that comprize 70% of my
visitors:Group 1, Group 2, Group 3 Currently, if I want to also look at
the other 30%, everyone else, I make a visitor segment that excludes
Group 1 OR Group 2 OR Group 3. This works for basic things, but as my
groups get more complex or more numerous, making those Exclude segments
gets very intensive. Then I end up with 4 segments: Group 1, Group 2,
Group 3, Other. For my particular situation, I'd like to be able to just
It would be awesome if we could get flexablility with the Everyone
Else/Other functionality, possibly combining these two ideas
This would be amazing. I am constantly making exclusive "Other"
segments, and they can become very process-intensive to build when they
are comprised of other excluded segments. (A few I could only create in
Ad Hoc, otherwise the Workspace Segment Builder freezes).
@JenlasserWould #1 apply to segment rows too? For #2, it would get
rather tedious if we have many dimension values, but in general, manual
reordering would be a decent stopgap for many of our problems. The
manual reordering would need to be able to be "locked" once we set the
order, because it seems like often the items get reordered if the data
gets re-ranked when it is refreshed. I'm going to keep hinting until
maybe it gets implemented: Can we just have a table builder in Ad Hoc?
@benjamingaines the auto-save is not working at all anymore, it seems. I
had to step away from my laptop while a table was querying. When I came
back, it said it auto-saved (and had the completed table) but when I
logged back in, the recent changes were gone.
Would love to see a true auto-save feature in Analysis Workspace like
there is in Discover/Ad Hoc. I always try to save early and often, but
I've lost work due to browser crashes or internet disconnections. In
Discover, this was mitigated by the auto-save feature that saved even
untitled/unsaved projects. There have been times when AH says it it will
have saved my progress (i.e. durring a disconnection) and will load the
last state after a reload, but then it is gone since the project was
In a perfect world, having one read-only option that locks down the date
range *and* one that allows date range modification would be great. If I
had to pick, I'd go for totally locked down first, since I have multiple
reports that wouldn't handle random date range changes well.