Error with new data integration engine, not using default schema

  • 30Views
  • Last Post 22 April 2020
  • Topic Is Solved
0
votes
Chadwick Smith posted this 15 April 2020

After I switch my package to "Use new runtime," I get the following error about the destination database: "Package failed: Table 'dbo.namb_accountmembership' does not exist in the database."

With the old runtime, it was using the tables in a different schema that I chose, the "crm" schema not the "dbo" schema.  This worked because I changed the default schema for the database login to "crm".  However, the new runtime is trying to force the tables to be in the "dbo" schema.

The source is Dynamics CRM and the destination is Azure SQL.

Order By: Standard | Newest | Votes
0
votes
Dmitriy Muzurov posted this 15 April 2020

Hello Chadwick,

Thank you for submitting a ticket with us.

We raised a request with our development team to investigate this.

Once there are any details, we will let you know.

0
votes
Dmitriy Muzurov posted this 22 April 2020

Dear Chadwick,

Skyvia has just been updated and the issue should be fixed.

Please test from your side and let us know.

0
votes
Chadwick Smith posted this 22 April 2020

Yes it is working now!  Thank you!

Close