Unable to cast object of type 'Newtonsoft.Json.Linq.JArray' to type 'System.IConvertible'.

  • 680Views
  • Last Post 31 January 2018
0
votes
Darshan posted this 25 December 2017

This is a Sev 1 issue as our reporting module invoicing and payments is completely down. Expecting prompt resolution. Also please share your support hours as it is not clear when you folks are available. The Skyvia support is very irresponsible which is causing me a lot of problems for my clients. If you guys are not even able to reply the customer queries it is useless to continue using your services.

Order By: Standard | Newest | Votes
0
votes
Mariia Zaharova posted this 26 December 2017

Please perform steps provided here. If this error still occurs, please tell us after which exactly changes (probably, you have changed the mapping) it occured.

 

Our working hours are between 06:00 GMT and 16:00 GMT. We are doing our best to process requests as soon as possible.

Sorry for inconvenience with this.

 

We are looking forward to your reply.

 

 

 

 

 

 

 

0
votes
Darshan posted this 27 December 2017

I have already tried the steps you mentioned last time here: https://support.skyvia.com/thread/qbo-to-mysql-updating-field-with-name-budgetdetail-attachableref-does-not-exist-in-schema-table/ for the error 

QBO to MySQL: Updating field with name BudgetDetail AttachableRef does not exist in schema table

which  led to the error: 

Unable to cast object of type 'Newtonsoft.Json.Linq.JArray' to type 'System.IConvertible'.

 https://support.skyvia.com/thread/unable-to-cast-object-of-type-newtonsoft-json-linq-jarray-to-type-system-iconvertible/. Please call me on +91 7259899085.

0
votes
Darshan posted this 27 December 2017

Nothing else has changed. 

 

0
votes
Mariia Zaharova posted this 27 December 2017

Thank you for the reply. We are investigating this issue at the moment, we will contact you as soon as any results are available.

0
votes
Mariia Zaharova posted this 31 January 2018

Unfortunately, we could't detect the reason of this issue. We would be grateful if you try detecting the table with which this issue occurs. For this, please create separate replication package for each of the tables and run it. We recommend you to start checking it for the Budget table.

 

Looking forward to your reply.

Close