Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Different sets of fields returned using api calls for prospects table #177

Open
tian-l-park opened this issue Mar 21, 2019 · 1 comment
Open

Comments

@tian-l-park
Copy link

Hi, I am retrieving records from the prospects table. My prospects table has more than 80 columns. A weird behavior happening is that my api calls will return 200 records with different number of fields, depending on where the offset is. For example, my first call with parameters sort_by = id and offset=0 returns 200 records with 82 fields, while another call with parameters sort_by=id and offset=20000 returns 200 records with 67 columns. Why is this happening and how can I avoid it? Thank you!

@creuzerm
Copy link

I think a Query tries to be a optimized and won't return all the fields if they are blank. If you want all the fields I think you need to do a READ.

I've had a query return headers and empty values even though there are values (CRM IDs I think it was) so I needed to do a READ to get the values.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants