Recent Report configuration changes are missing after the Winter ’06 Upgrade

I wanted to see if anyone else is having the same problem I am with the Salesforce.com Winter ’06 release…

I did a lot of work on Reports this past Friday for a training session I am conducting on Monday. I went into the upgraded config and noticed that all of my report changes made Friday are missing. It’s strange. Other configuration changes like Field Level Security changes made it, but the reporting changes did not. The changes I made on Friday were for reports that were created a few days ago, but I had gone through each of them on Friday (about 20 in total) to adjust columns, filters, etc. in order to standardize them across different user groups. All of those modifications made Friday are missing.

Anyone else have an issue with this?

2 Comments

  1. Aiden Said,

    January 10, 2006 @ 6:39 am

    Hi,
    An important report bug that I’ve noticed is that the columns used to group reports are no longer selected in the “Select Columns” or available in the “Set order of columns” step of the report wizard. The net effect of this omission is that any reports that are exported to Excel (via the app or the Office Edition) have a messed up column order. The columns used to group a report now show up at the end of the report. When I use a column to group/sort a report, I place them in the front of a report to make the report easier to read. Moreover, Excel macros and Pivot tables that I’ve created that rely on column order no longer work.

    Aiden

  2. Dan F Said,

    January 26, 2006 @ 11:00 pm

    Hello, I’d like to report that I’m having widespread problems at my company using Outlook Edition 2.0. It seems to be causing Microsoft Outlook 2003 to stop responding for seconds at a time and it is MUCH slower than the old version. I am disapointed that they would release such a buggy app. I have a ticket submitted and they commented that it is a known issue and they are planning on releasing a patch “shortly”.

RSS feed for comments on this post