Newbie Creating Pipedrive to On-Premise SQL Server Flow -

Integrator.io
1

Hi Celigo-ites,

I created a flow, "Pipedrive to SQL Server - Deals - Bulk Import". I made sure the mapping referenced a name value pair and not an object.

-I then received this error:

image
image1118×194 16 KB

My source for id is $.id and I mapped it to deal_id (in the sql server table).

-After receiving that error, I modified my table ddl to include a column titled, "id", and then I received an error like above for the source name/value pair, $.title, which I had mapped to deal_title. Next, I add a column to the table called, "title", and sure enough, I receive an error like above for the column, currency...

-It is interesting that it seems "to want" me to make the table name columns to have the same name as the name/value pair. I kept on adding column names to correspond with "its expectation." It kept erroring.

-------------------------

Next, I took the approach of simplicity (make the mapping super simple and surely it will work).

-I did modify the mapping to be very simple (e.g. id column and a handful of other columns).

image
image866×496 24.9 KB

When I did this, it threw this error:

image
image1094×382 38.7 KB

This column which is part of the name/value pairing from the deal json, is not even a part of the mapping.

I figured I could make the mapping trivial as possible and get it to work, but it never works for the bulk sql import.

I am able to get this working (without any error) using single record SQL inserts.

Does anyone use bulk import to SQL from Pipedrive?

Has anyone had success with bulk imports to a SQL Server database?

Thanks,

Patrick

2

Hopefully it's as simple as missing this mapping. You should have $ there. Since nothing is there, you're essentially bypassing the mapper altogether, which is why it's expecting exact column names as the source.

image
image1720×984 111 KB

3

Hi Tyler,

Thank you for your answer. I did take a look and try with the direction you provided ($ on the right hand side of the mapper). I received similar errors like above. After further review, I see that the bulk insert SQL approach is only for the cloud here, Import data into Microsoft SQL – Celigo Help Center. If this is correct, I have to approach this differently (e.g. single record).

I have built single record insert statements using handlebars and it is working (kind of ugly and I am using the “updated since” parameter with a literal :).

I am not planning on configuring this in the cloud at this time. If we stick with this hybrid flow, I guess this is the best approach and it is “good as it gets”?

Thanks!