Skip to main content
sarah_post
Helper ⭐️
December 4, 2018

Zendesk Fields - Need to Change Field Types

  • December 4, 2018
  • 6 replies
  • 55 views

On occasion we need to to change the field types in the Zendesk object but cannot because this is a system object. Example: Ticket Id is a Number field so it shows in the UI with a comma, e.g. 60,002 when it should appear as 60002. It's not a true number but is an Id field - except it's set as Number by the system. Can we look at ways to make this more admin-friendly in the future?
 

    6 replies

    dan_ahrens
    Expert ⭐️⭐️⭐️
    January 15, 2019

    Thanks for sharing this Sarah. We'll take a look at our options on this and get back to you.
     

    VP of Customer Success at Forcepoint
    dan_ahrens
    Expert ⭐️⭐️⭐️
    January 18, 2019
    Hi Sarah, can you share a bit more about the use case that would require you to have a ticket number without the comma delimiter?

    VP of Customer Success at Forcepoint
    rozi_shuster
    Contributor ⭐️⭐️⭐️
    January 20, 2019
    as this is a ticket number , it should be as a whole number without commas. when we copy the case to zendesk to search we need to delete the comma.

    it is not critical, but it is cosmetic and needs to be corrected, as this number isn't a currancy.

    dan_ahrens
    Expert ⭐️⭐️⭐️
    January 23, 2019
    So in this case it really should be treated as a string and not a number, correct?

    VP of Customer Success at Forcepoint
    sarah_post
    Helper ⭐️
    January 23, 2019
    Correct. It happens to be a number, strictly speaking, but a case # should never be treated as a number (could have characters in it, other systems don't treat it as a number, etc) and string would be the best way to think about it.

    lori_dinardo
    Contributor ⭐️⭐️⭐️⭐️
    September 9, 2019

    I am having the exact same issue. Not only is it an Admin issue but it looks horrible on reports. Even some of the ID's contain commas. I was recently told that it was a string in the object but it's displaying as a number on the screens and reports. This is where the problem lies. Users don't want to see an ID or ticket number containing a comma.