Yesterday I got myself a Failed to schedule report error.
After some testing I found the reason: Don’t use a double quote as the first character of your Dashboard name, as this will effectively prevent you from setting up scheduled deliveries.

I myself find it a bit annoying, so I started digging into what’s actually happening to those settings when you hit the Save button.
The explanation is quite funny, only a few of the settings are actually saved in the way you would expect them to be saved, that is as properties tied to your login. Most of the settings are only stored locally on the computer you are currently using to change the settings.

The settings you can count on are :

• Include Calendar Events in Reports
• Enable network acceleration for improved report performance
• Currency
• Scheduled Report Encoding

The rest, you’ll have to adjust on every computer you use for SiteCatalyst.

Workaround:

• Setup your report suite to display a Dashboard as the SiteCatalyst startpage.

I’ve especially noticed a minor change made to the conversion classification editor.
Prior to the 9/17 maintenance release, deleting a child numeric classification was impossible, You got no reaction from the editor when trying. This behaviour has changed a bit, trying to delete a child numeric classification now results in the parent being deleted instead, and when you recreate the lost parent classification the child magically re-emerges as well.
I’m still trying to figure out the purpose of this change.

Update:
Here is a video demonstrating the strange conversion classification editor behaviour.

Click here to view the embedded video.

Sorting
Numeric Classifications creates new metrics you can use in your reports.
I would expect any new metric, numeric, or otherwise calculated, to behave just like any build-in metric in regard to sorting.
Metrics normally sort in descending order in SiteCatalyst, Numeric Classifications not being the exception, but they are not sorted on the actual value of the metric, the sorting is performed using the user provided values used to multiply by the existing metrics (Click-Throughs, Units, Orders etc).
Bottom line: Numeric Classification metrics don’t sort.

Totals
Sometimes the totals on our Numeric Classifications are working, sometimes they are not (total=0). It’s possible there is a pattern, but I haven’t been able to figure out what that would be.

The “Targets editor” has been fixed. This is really great news, the targets editor has been broken for almost a year. You’ve always been able to create new targets, but editing existing ones wasn’t working, in the beginning all conversion related metrics were missing from the dropdowns when trying to edit a target, but then as part of the SiteCatalyst 14.6 release, the editor became completely broken, all metrics were missing when trying to edit a target and a few javascript errors were also included.
This has all been fixed now. Perfect ?
Close, but not 100%, as usual, engineering didn’t bother testing on any foreign character sets, so at least Danish characters aren’t supported in the dropdowns.

For those unfamiliar with Danish:
bredbÃ¥nd is supposed to be bredbånd
søgeord is supposed to be søgeord

Clickmaps: Finally Omniture is moving towards supporting the BUTTON tag in Clickmaps, if you add a s_objectID in the onclick handler of your button tags, you can now be pretty sure those buttons will show up when turning on the Clickmap plug-in.
I think it’s great news that Omniture has started fixing some of the Clickmap issues, but there is still a long way to go before things are working as specified in the Clickmap user manual.

Update
I just noticed yet another thing that slipped through the release testing at Omniture.
In the Targets Manager, all target names now have the textstring Name prepended.
If You create a target with the name Sales, it will show up in the Targets Manager as : Name Sales.
I know it’s no big deal, it just looks sloppy, but I guess we’ll get used to those new names.

Then one day I realized that I had hidden a menu that I on rare occasions actually need. This is where the “Show Omniture’s default menu structure” is supposed to come in handy, you’ll find it in the “My Account -> Report Settings” area.
Unfortunately it isn’t working, checking this option changes absolutely nothing

Under certain circumstances the reports from SiteCatalyst can become really … well lets just say, less useful.

It may be difficult to imagine how a few character encoding issues can affect SiteCatalyst that much, a demonstration is needed.

On our site we have a search enabled FAQ, we capture all search phrases in a prop, this prop is correlated with another prop containing information about our Site Sections, we use this to break down the search phrases into Business and Home user search phrases.

A report could look like this: ( The date showing 1 Jan 1969 – 1 Jan 1970 is just a sideeffect of the latest Omniture maintenance release, and not relevant for this demonstration)

Now let’s try to apply a filter containing some Danish words… Like: netværk OR spærring
In return we get a report with no results … strange, after some double checking it’s safe to conclude that filters containing Danish characters won’t work when a correlation has been applied as well.
Let’s try removing the Danish characters and repeat, so now we filter : netv OR rring
Oh yes, much better, but the graph isn’t nice looking anymore, it contains some strange mix of Danish and I guess it’s Japanese.

Now what? such a report isn’t really suitable for distribution. I guess we could download a PDF version instead? Bad idea, that’s even more broken. Graph is the same, but text gets truncated at first occurrence of a Danish character.

Excel or Word downloads ? Well unfortunately they are also broken.

Just after creating a report for a Dashboard everything looks nice:

But if I try to edit the report from the Dashboard, the character encoding problem shows up: