AutoInc unique identifiers are not supported for MsSql backend

[James Legan]

I just updated a few minutes ago as soon as I saw that default value support (including sequential guids) was supported. I created a test method in my project and confirmed that in fact a new record with a sequential guid is in fact now being inserted without having to go through my stored procedure and all worked as expected (yay Telerik).

However, in my Error List I now have a permanent error that reads "AutoInc unique identifiers are not supported for MsSql backend." Double clicking on it brings up the OpenAccess validation window and a "fix" wizard which allows me to select a different key generator. In the combobox I am able to still select Autoinc and it still works. 

Is there actually a bug here or an overzealous validator with nightmares of its past love-hate relationship with sequential guids?

[James Legan]

Converting to a bug due to lack of response.

[David]

I also recieved this error after upgrading.  In my case I have a view mapped in my domain model that has a composite key, multiple identity fields.  The solution runs, but the datagrid that pulls from that view is showing duplicate rows. 

[PetarP]

Hello James and Joshua,

 As we have already confirmed - this is indeed a bug that will be fixed for the next release. Anyone encountering this error message should disregard it as it is only a warning that something went wrong while it is actually working as expected (its an old validation rule that needs to be removed).

Greetings,
Petar
the Telerik team