Forum Discussion
CRM Service Reporting - Best Practices?
I have a blog article on this, although not specifically for the Ticketing stuff. However it may have some helpful tips. For example, I created an Azure Data Marketplace feed that turns the various status codes into human readable things.
You could also try the CRM Online content pack in the Service. It builds a dashboard focused on sales but the data model it creates already does most of the expansion and turning the esoteric codes into something useable.
Hi and thanks for your reply. Yes I am well aware of your blog post and had hoped I could find something analogous for cases. I will review it again more closely for the status code decoding bit.
Sadly, the CRM Online Content Pack is pretty much useless to me since it doesn't pull in the IncidentSet or QueueItemSet tables. Also, I had tried to pull it in a couple of days ago, but it stopped loading for me - PBI says it fails to load the tables for some reason.
Yeah, I am strugglin a bit with the CRM tenant upgrade to 2016. Not sure if this is the source of your problem also. Seems that the old OData url feed "works" but my models won't refresh that way, they now error out since going to 2016 in the CRM tenant. The new OData feed URL doesn't work with the content pack and I'm assuming that if I use the new OData feed URL I have to rebuild all of my models.
:(
