This post is a part of a series of posts for Customer Service. The complete GUIDE can be found here
Why on earth did anyone think that this was a reasonable number to include in Customer Service cases?
This number is way to hard to relate to, and too hard to explain why came to be. It has absolutely nothing to do with the Email Tracking Token, leaving the customer utterly confused when talking about numbers.
Might be a little hard to see here, but I open my solution from https://make.powerapps.com and select the case entity. In the Case entity I have the default Case Number field. When choosing to edit this field I simplify the autonumber. This will make even more sense later on.
All of this will be included in my Customer Service Solution later on in the guide.
3 thoughts on “Dynamics Customer Service Autonumber”
Enkelt og veldig smart – betyr mye for kunden. Tenk om vi da kunne hatt en epost sporing som bygget på ditt nye [case nummer] – [serienummer på epost]
Det kommer i post nr 9;)