exporting call stats to .csv

[goland]

Hello,
I have a request to export call stats from symposium to some form of text file, preferebly .csv
My knowledge symposium is new and somewhat limited.
I would like to be able to export this data to put into an external Db for reporting.
The client requests some data like the following:

Call Date,Call Time,Offered,Accepted,Abandoned,Queue Wait Time,Call Duration,Staff ID

I can view all the reports on the webadmin side and even GRTD but not sure how to access this data?
ANY Help would be GREATLY appreciated.
Thanks,

 

[KillianK]

Start with Excel, "get external data", "new data base query", setup a username in symposium, best with full rights. You can connect to the sql database, with your username and pwd, create a pivot table or get a list of users to start so you can get familar with the fields? This works with crystal too.

Cheers,

Killian,

NextiraOne Ireland

http://www.NextiraOne.ie

 

[PhilMyWallet]

I have a similar problem to this.

I want to export a report to excel from Symposium. I need the columns to be together without blanks.

This works fine if I use Crystal (v.8) to export the reports into excel. However when I import the report into Symposium, the data exported (into excel) leaves several blank columns between each field. I have tried to use excel data only, this returns the same.

I use Symposium v. 4.5

Any ideas??

 

[DoubleDyno]

We have the same problem here. From what I've been able to find out so far, this is as planned by Nortel. Excel exports will use merged cells and will require manual manipulation.

If this is not correct, please tell me and let me know how to export the data to excel without merged cells and the data in contiguous columns. My vendor will be opening a support ticket on this issue for Nortel to address.

Currently, our web server is in a separate domain using Win 2000 Server. Once I get our custom reports ready, we plan to migrate to a Win 2003 server on our domain.

I cannot get scheduled reports to run, but believe that it might be due to the separate domain. I'm hopeful that the migration may allow scheduled reports. Then, I can export to .csv and other file formats unavailable from an Ad Hoc run which may circumvent the merged cell problem.