I'm developing a facility to mediate between a SQL database hosted on Azure and MailChimp's ListMembers table. Skyvia seems to be the right tool - great.
Your connector to SQL correctly requires that the target SQL database has a primary key. So I create a DT_WSTR compliant field called 'Id' in the SQL table and declare it as a primary key.
MailChimp 'ListMembers' has a matching field, but Skyvia's matching screen does not show primary key fields on the matching list. So you would think that there is some default matching taking place maybe.
However when I run the task I get the error "SQLite error no such column: REF_ID_Id".
Maybe this is a bug -- unless I'm doing something wrong?
(BTW I have tried this process using the MailChimp API 2.0 and 3.0 Skyvia connectors. In both cases the SQL table's primary key is not shown on the matching screen and running the task throws the 'no such column' error for the primary key. In MailChimp API 3.0 the error is 'Invalid column name [column]. Invalid column name [column].')