Exporting data to a JSON, CSV, or XML file

Return to top

43 Comments

  • Anne Ronalter
    Zendesk Customer Care
    Hello,

    it seems like the function is not yet enabled for your account.

    To do so, I will go ahead to open a ticket on your behalf.
    -1
  • Mukesh Kumar

    Hey Team, 

    I have been working on the data export and getting to know it slowly. I must say JSON export is great to view the data. 

    I have a question though, like JSON, where you can define a date range and data type, can we not do the same for XML / CSVs?

    When using these options, the text files are way too big to be opened to view. What is the best way to pull/filter the data using a date range/data type for XML / CSVs? 

    0
  • Tony
    Hi Mukesh,
    thank you very much for your comment. I'm glad to hear that you really like JSON export.
     
    So, as it is now, the Full JSON export is the only one capable of defining a data range and data type, as you already know.
     
    However, there is a small margin in which you can play with CSV exports. You can export a view to a CSV file, or you can use Python for it.
     
    Or, you can use our REST APIs endpoints to get the information you need, then after you can use Python for compiling the JSON to CSV, so you have only the information you want.
     
    I hope that helps!
     
    -1
  • Aleksandar Salevski

    Hi All, the problem with this JSON is that there is no comma "," between users, any help with this one?

    0
  • Nghĩa Hồ

    Hi, i don't see Quick Look:  Admin Center > Account > Tools > Reports, although my account is Growth plan

    0
  • Comdata, Inc.

    The instructions updated on 11/03/2022, state to go to Account > Tools > Reports. 

    There are no Tools or Reports sections. We are an enterprise customer. A lot of this is inaccurate. We're dead in the water trying to export our 4000 organizations to updates them, because you all only put a CSV upload, but no download....geeze!!

    1
  • CJ

    You might be able to force your way to the page via this url, you'll need to put in your own Zendesk domain: 
    https://domain.zendesk.com/admin/account/tools/reports

    1
  • Comdata, Inc.

    Unfortunately, that is a dead link.

    0
  • Amy Dee
    Zendesk Customer Care

    To Aleksandar Salevski - the JSON export tool uses NDJSON, or "Newline Delimited JSON" format. This format returns a series of standalone JSON objects separated by line breaks. It's optimized for streaming extremely large sets of data into a database, where a single file would be too large to handle effectively. If you want to convert the entire export into a single standard JSON file, you'll need to add commas between the lines and a "users" wrapper around the list.

    To Nghĩa Hồ and Comdata, Inc. - data exports are not enabled by default. They need to be turned on before you can use them. If you don't see account export tools in the Admin Center, it means one of two things: exports have not yet been enabled for your account, or exports are enabled but there is a domain restriction blocking your access.

    If exports aren't enabled, the account owner can reach out to our support team to have the feature turned on. If exports are enabled, the account owner can modify or remove domain restrictions on the export page. (The account owner can reach the exports page even if their domain does not match.) 

    I hope this helps!

    -2
  • CJ

    Amy Dee 

     If that's the case, it would be great if the entire article were re-written to reflect that this is no longer available in JSON. This is a bit like changing the article language from French to Spanish and saying it's still available Spanish because they are both Romance languages. It's not JSON anymore, and that means that JSON parsing in code will not work. My scripts that know how to read JSON, but cannot read NDJSON, because it's not the same language. This is why people are telling you that your JSON exports are broken. 

    1
  • Amy Dee
    Zendesk Customer Care

    Hi CJ - Thanks for following up! There may be a misunderstanding here, so I want to clarify a couple points.

    • This isn't a recent change in behavior. This is how the account JSON exports have behaved for a long time. Our documentation has also included instructions for converting the files for some time, though it wasn't always clear why that was necessary.
    • We did rewrite the article to make this clearer. The changes were published over the summer. The article now includes a description of NDJSON, a link to more resources about it, and instructions for converting the export if you want to open it as one file.
    The JSON export from Zendesk includes data in JSON format. However, these exports are far too large to open as single files. Most JSON parsing tools will fail with relatively small date ranges. That's why we chose to use NDJSON. That format optimizes the export for streaming and makes it easier to pull individual tickets, users, or organizations from the file.
     
    If you prefer a single (massive) JSON file, you can easily automate the conversion. It just takes commas at the line breaks and a static wrapper at the start and end. Yes, it's an extra step, but it's a relatively simple one. 
     
    We're always reevaluating our articles to make the content clearer and more accurate. Comments like yours help us find places that need updates. Thanks again!
     
    -2
  • Comdata, Inc.

    CJ FINALLY, someone who knows what they are talking about...getting a sincable or timely solution from ZD is near impossible. They just need to allow for table access to our instances so we can just connect, pull, and be done. Instead, I've had to jerry-rig the same through AWS. It's a nightmare. Never seen a ticketing product where I cannot readily access my data for the purpose of maintaining data integrity, or making bulk changed.

    0
  • Comdata, Inc.

    Amy Dee the only problem is that Zendesk makes zero effort to tell us what is or is not turned on. I had no clue this option even existed. So I had to go out a buy a 3rd party app (again)...and spent considerable amounts of time trying to get data exports setup in AWS to automatically pull data. I literally pleaded in a meeting with ZD this week to tell me WHAT ELSE is not turned on. I'm an enterprise customer, turn on everything, or at the very least tell your customers what you have turned off. The only way I even know that the ADMIN > Tools > Reports option even exists, is because an end user made a post (not ZD). So I have to contact ZD to turn on the feature. And once it's finally turned on, its just a bulk dump, with date range. Absolutely no filter options. You all need to read these complaints. Some have been open for years with no resolution. I don't want JSON exports, I want access to tables and my customer fields. I go into reporting now and try to pull an Organization report, in your cube environment, but the datasets are only ZD, not our custom fields. 100% USELESS. 

    0

Please sign in to leave a comment.

Powered by Zendesk