You’re offline. This is a read only version of the page.
105
If we have requirement that can be solved by using separate queues (single/multiple teams can work on each queue ) or different views , then which solution is better w.r.t performance and future support/enhancements from CRM?
*This post is locked for comments
I have the same question (0)
You would use Queues if you needed to create a central pool of multiple different types of record (e.g. cases,tasks, leads etc.) that teams could pull off and work on items without changing the ownership of the actual record it's self. The QueueItem wraps the actual record so that it can be routed/and worked out without updating the record it's self. This is good for support/triage type situations.
Queues are also email enabled so can send/receive emails into the queue it's self.
Views will only show a single record type (with the exception of activity views) and can only be filtered based on the actual data in those records - so if the data changes, the view will reflect that. One a queue item has been created, it can only be removed by acting on the queue item its self.
Queues & views will both be supported in foreseeable future I'm sure!
As for performance - when you look at a Queue - it is actually a view of Queue Items, so factors such as number of records, filter criteria, number of columns will affect the performance of both Queues and Views.
You could assign records to a team and have users assign them to themselves if you didn't need to retain the original owner or have the need for a central view of multiple record types in one place.
hth
Share
Report
All responses (
Answers (
