Sign in to Community
Sign in to view all badges
In SiteCatalyst, I'd like to see a trend of the number of Orders for which a specific eVar is NOT being set (aka: "None"). "None" does not show up in the Graph, even though it should.
Instead, the graph says "There is no data for the selected criteria" when I filter to just None. Why?!
If I'm understanding correctly, this is possible today. Go to My Account > Report Settings and check the box that says Show "None," "Unspecified" and "Typed/Bookmarked" data in report graphs. Then you can trend None on any report.
If this doesn't meet the need, please let me know. In the mean time, I'm marking this as Already Offered.
So I tried this several different ways, and it just seems like it doesn't work as expected. At first I just switched to Trended view, but "None" was not shown in the Top 5 (even thought it was #1).
Then I tried filtering the Ranked report to just None, then switching to Trended, and again my None filter was removed, and the Top 5 were shown (without None).
Then I tried switching to Trended, and clicked "Select New". I searched for None in the popup. Instead, Unspecified showed up. Strange. I tried adding just Unspecified and the selection box refreshed without any items selected. I tried several times, same issue. I then tried adding Unspecified and another item or two, and that works, occasionally...
I thought maybe I was having browser issues, so I logged out and logged back in. Same issues.
Anyway, why is it called Unspecified in the Selected Items popup, but None in both the Trended and Ranked views of the report? Confusing.
For whatever it is worth, I pass a hard-coded value like [NO STATE} to my eVars to get around this issue...I agree that it should be made easier, but if you want a short-term fix...
Thanks for the idea, but I'm worried about over-writing eVar values that have already been set.
Do you pass [NO STATE] in on every eVar at initial landing of every user? What about for eVars that have longer Expirations than Visit (say 2 weeks or Never), wouldn't that over-write your data?
Or do you have some code that checks to see if the eVars have already been set? I'd imagine that's the only way to get around this.
Hey Brett and Adam,
Just checking in on my responses on this one. The issue came up again recently.