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:
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).
When I did this, it threw this error:
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
