The specified value is not an instance of 'Edm.Int64'

[johnselkirk]

I am trying to update a double value using DotConnect version 4.2.132.0 and .NET 3.5.

When I try to save the changes on a new row I get an error saying :

The specified value is not an instance of 'Edm.Int64'

When I implement the code using .NET 4.0 I don't get the issue but I am bound to 3.5 for the project deliverable

I have created a small sample that reproduces the error and it is on dropbox : http://dl.dropbox.com/u/2292728/TCT/Dev ... eIssue.zip

Any advice would be GREAT!

[Shalex]

We have reproduced the problem and are investigating it.

[johnselkirk]

Thanks,

Any idea on when there will be a fix or steps to workaround/resolve?

I am on a project timeline so just need to manage expectations.

John.

[johnselkirk]

I figured it out.

It was not the X, Y double columns it was the SeqNum column (Int32) that was defined in the SSDL as integer. This has not been a problem in the past but that column is part of the Key so it may make a difference.

I changed the SSDL type for the SeqNum to int32 and all is well.

Thanks for your help.

[Shalex]

Thank you for your feedback.

[Pauli]

Thank you John for informing the solution.

I also had same problem. I tried to found from other places until I found your solution.

From Devart people I ask, why my int32 fields has been changed to integer? I have made all changes witn ENtity Developer.

[Shalex]

From Devart people I ask, why my int32 fields has been changed to integer? I have made all changes witn ENtity Developer.

Could you please give us a detailed description of the problem? If possible, send us a test model and specify the exact steps we should follow to reproduce the issue.

[Pauli]

Hi
I happy that everything works now and I am too busy to write more detailed description or try to reproduce the situation. I don't know why Entity Developer changed int32 fields to integer fields.

If I find out something then I will inform you.