SQL Server data type FDO Conversion Failure when Checking In features

[Anonymous]

Hello, I am having difficulty exporting new features into my SQL Server table. I have tried to create new features from geometry. The record is entered into the data table once the feature has been created and all records are null. However, when I choose to check in the new features, I receive this error:

Feature was not saved in the target feature source.

2=RDBMS: [Microsoft][SQL Server Native Client 11.0][SQL Server]Conversion failed when converting from a character string to uniqueidentifier.

1=Failed to execute Fdo command.

Failed to insert feature.

dbo:cable (), Rev# <0>

Failed to save edit set.

Rollback failed for all feature sources.

Failed to insert feature.

Failed to execute Fdo command.

RDBMS: [Microsoft][SQL Server Native Client 11.0][SQL Server]Conversion failed when converting from a character string to uniqueidentifier.

Failed to save edit set.

Neither Bulk Copy, nor the Export to FDO functions work either. The system crashes in my attempt to use these tools. I have a feeling that these issues have the same causal factor as it has to do with the databases ability to convert the primary key. Any help solving this would be greatly appreciated.

[kalman_albert]

Perhaps you try to insert a new feature in a table where you set field as unique identifiers. This is a bug in provider (in my opinion) or the provider can handle this situation. We have had the same problems in a replication database. We solve as workaround, you need to make a "editable view" and in view you should not select unique identifiers. Unfortunately is undocumented at Autodeks how to handle the situation in a replication database, huge problem.

The problem is because who develop the provider unfortunately did not care how we will use it. Because unique identifiers is managed by database, when you make a new feature (normally as we expect) the provider should be first get from database the value to complete, but no, it will set as null and when you make a check-in this is send to database and trying to write null or "" string in this field what is deny. 

Also is a big problem with a situation when you set as default value for a a filed through a function (in default value you write a function).

We open a long detailed case for this problem ... but ... nothing, I did waste my time .

A second workaround is to set  your Primary key as "Identity" and you'll have no any problems.

Albert