Reporting Attributes Changed After v20 Update to u6 RC3

Status
Not open for further replies.

cpe90

Customer
Joined
Mar 7, 2023
Messages
78
Reaction score
19
Before (v20 u5 Build 20.0.5.551)
1755886517464.png

After (v20 u6 rc3 & v20 Update 6 Build 724 Release)
1755886683526.png
We are experiencing some issues regarding our Call Reports showing different information inside our "From" Attributes after updating to v20 u6 from u5. Previously our reports included our Department/Queue/DID rule name which allowed for our Data analyst to sort incoming phone calls per building or department but now after updating we are only being shown the raw DID number in the "From" collum.

From some research I've done in previous versions there was a setting you could toggle on and off to prepend or append Department/Queue/DID rule name information to the "From" collum under Admin Console --> Contacts --> Options but has since been removed from current versions. We haven't made any other changes to our system.

My question is in the current version we're using right now, which is v20 Update 6 Build 724 Release, can we include the Department/Queue/DID rule name in the "From" Collum or implement a workaround for Call Reports?
 

Attachments

  • 1755886612132.png
    1755886612132.png
    15.3 KB · Views: 0
I think I've found the source of the issue.
I wonder if there's a way to delete this thread?
 
Hello,

Please confirm if you would like me to delete the thread.

Best,
KS.
 
Not sure if you'd like to delete this forum or not but we found that this issue stems from the reporting overhaul that was done from v20 u5 to u6. I'm not sure on the specific of what was done but it looks like what we we're trying to accomplish with this reporting (tracking inbound calls, who called, what number was dialed and where it was routed) can all be done through the new "Inbound Calls" feature which adds a separate DID number collum to track what number was dialed when the person called and where/who it was routed to.

Just thought I'd update to see if this thread could stay open in case someone else was having the same issues.
 
  • Like
Reactions: KyriacosS_3CX
Hi,

Now that you have the solution to your issue written, I'd rather it stays. Will lock it though to keep things clean. Thanks!
 
Status
Not open for further replies.

Members Online Now

Forum statistics

Threads
111,831
Messages
589,277
Members
164,660
Latest member
RJenkinsROCK