Hey everyone,
Thank you for bringing this issue to our attention. I'm sorry if you've been informed that it's an unsupported piece of functionality, but it actually should be supported. That is a bug, and I've filed a ticket for my dev team to take a look. We'll work on getting it resolved as quickly as possible for you.
------------------------------
Maisey Harris
Development Group Manager, Analytics UI & Reporting
Genesys
------------------------------
Original Message:
Sent: 08-23-2019 06:39
From: Juha Niinimaki
Subject: Export data in Queues Performance view not working if using Division as filter
Thanks Richard. I think I have votes available, but I'm not going to raise a feature request. In my opinion this is a bug and I hope Genesys will fix it. Our partner promised to discuss with Genesys.
------------------------------
Juha Niinimaki
Konecranes Oyj
Original Message:
Sent: 08-23-2019 03:45
From: Richard Chandler
Subject: Export data in Queues Performance view not working if using Division as filter
I raised a case about this previously. It's not an issue. Filtering by Divisions does not allow export from Performance Views. I was informed to raise a feature request but I have no votes currently available.
------------------------------
Richard Chandler
G3 Comms Ltd
Original Message:
Sent: 08-22-2019 11:17
From: Marc Moynan
Subject: Export data in Queues Performance view not working if using Division as filter
Juha,
We have the same issue - we've opened a ticket.
Marc
------------------------------
Marc Moynan
Canadian Dealer Lease Services Inc
Original Message:
Sent: 08-22-2019 04:15
From: Juha Niinimaki
Subject: Export data in Queues Performance view not working if using Division as filter
For some reason we are not able to export queues performance view data to a .CSV file when we are using Division as a filter. When clicking the Export CSV button we get Failed to Create a Report! notification. Export works fine when using Queue as a filter. I checked already the permissions. Analytics > Data Export > All is correctly set. Has anyone else had the same issue? What could be causing this?
#Reporting/Analytics
------------------------------
Juha Niinimaki
Konecranes Oyj
------------------------------