Badges
Accepted Solutions
Likes Received
Posts
Discussions
Ideas
Blog Posts
Hi @SanfordWhiteman, The issue persists even after removing the ID column. GET /bulk/v1/leads/batch/{id}/failures.json no longer returns the ID column which is correct, since the original Bulk Leads Import request doesn't include ID. However, the core issue from the GET /bulk/v1/leads/batch/{id}/fai...
Hi @SanfordWhiteman, Prior to November 5th, the GET /bulk/v1/leads/batch/{id}/failures.json endpoint consistently preserved all columns from the original CSV, even when fields contained blank values. The endpoint did not remove empty columns or shift data into earlier positions. Using the same examp...
Hi @SanfordWhiteman , The failure reason were: "Value for lookup field 'email' not found". From the tests, ID was not a required column, for example if the original CSV had the following data:ID,firstName,lastName,email,phone1001,NameA,SurnameA,emailA@email.com,1234567891001,,SurnameB,emailB@email.c...
Hi, Recently the Get Import Lead Failures endpoint (GET /bulk/v1/leads/batch/{id}/failures.json) started returning data that differs from the original CSV uploaded for Bulk Leads Import.The process:Bulk Leads Import (creates job from CSV)Get job status (check for failed rows)Get Import Lead Failures...