Export feature returning error on objectProperties

[knorfleet]

I am attempting to use the new export feature for tickets, I have code the pulls the entire ticket list today, but it runs for hours. With the export, everything works fine if I do not include any objectProperties. I carried over the same list of fields from search properties, but I receive an error "{"status":"error","message":"Please fix or remove these properties as they are not a part of the object:"... when I include any of the fields I need exported.

I have used the API to validate these fields and they work for a full pull or recent changes, but do not work at all for the EXPORT API.

Any help would be greatly appeciated!

[knorfleet]

I tried to run the export again with fewer fields and different combinations to no avail. Only an empty objectProperties appears to work....

{'exportType': 'VIEW', 'exportName': 'Tickets_Name', 'format': 'csv', 'language': 'EN', 'objectType': 'TICKET', 'objectProperties': ['ticket_type,category,ticket_id']}

resulted in a 400 response:

 "status":"error","message":"Please fix or remove these properties as they are not a part of the object: ticket_type,category,ticket_id"

Any ideas?

[knorfleet]

No I have not made any progress. They are a combination of both custom and default. I can receive data back though. I tried with smaller properties, but will try again with other combinations.

"abandon_rate,createdate,hs_ticket_category,elmlink_create_date,elm_product,ticket_type,subject," "hubspot_owner_id,hs_pipeline_stage,ticket_created_by,hs_pipeline,hs_resolution,hs_ticket_id," "source_type,queue,work_count,future_due_date,closed_date"

[Jaycee_Lewis]

Hey, @knorfleet 👋 Did you make any progress here? Are these custom properties or default ticket properties?

If not, can you share a simple example request:

• using the Search API and one property
• using the Export API and using the same property (that fails)

Thank you for the additional details! — Jaycee

[knorfleet]

Can you help me out?