Forum Discussion

EdwinReik's avatar
EdwinReik
Qrew Member
3 years ago

Building URL to download CSV

I'm building some automations outside of Quickbase and have found the best way to pull data has been to build a URL using a usertoken that pulls data into a CSV that I process externally with python....
APIs and custom code
BlakeHarrison's avatar
BlakeHarrison
Qrew Captain
If you use the last URL you mention and include the CSV option and it's downloading the wrong fields, I'm going to guess it's downloading the default fields for that table. Most likely, you'll need to include the 'clist' parameter to identify the fields you want to download.

------------------------------
Blake Harrison
bharrison@datablender.io
DataBlender - Quickbase Solution Provider
Atlanta GA
404.800.1702 / http://datablender.io/
------------------------------
EdwinReik's avatar
EdwinReik
Qrew Member
3 years ago
I think that we're getting close but not 100% that this is the right solution. 

When I use this method: 
'https://eagleview.quickbase.com/db/bpw3pr8nu?a=q&qid=31' + '&opts=csv' works when I'm signed in.​

the csv that comes out is named X.

But when I use the final method mentioned above:

'https://eagleview.quickbase.com/db/bpw3pr8nu?a=api_genresultstable&qid=31&usertoken=*secret*' (no mention of options csv) opens a page with the correct table present, but doesn't download the csv. This works when I'm not signed in.

when I do the same as above but add '&options=csv' it downloads a CSV, but not the one that is being shown (same wrong one as mentioned above)...

the csv comes out named Y. 

I don't believe it's a matter of adjusting clist but I really have no idea. I think it's actually pointing in the wrong place



------------------------------
Edwin Reik
------------------------------
  • BlakeHarrison's avatar
    BlakeHarrison
    Qrew Captain
    3 years ago
    "bpw3pr8nu" is the table DBID in your URL. Is this the correct DBID for the table where you want to pull information from? If so, then it's not possible that your URL is pulling information from a different source. According to the API documentation, if you utilize "API_GenResultsTable" and do not include the 'clist' parameter, it will return the fields that are included in the default report for that table. If those are not the fields that you are expecting / needing, you will need to include the 'clist' parameter.

    If the DBID is correct, I would compare a sample of the data you're downloading to the data as it appears in Quickbase. If, after doing that comparison, your download data does not appear in the records in Quickbase, I would suggest you submit a support ticket.

    ------------------------------
    Blake Harrison
    bharrison@datablender.io
    DataBlender - Quickbase Solution Provider
    Atlanta GA
    404.800.1702 / http://datablender.io/
    ------------------------------