sql table with uniqueidentifier not showing as autoguid

Hello @braddo 

Thank you for your question. This is my opinion regarding your database structure. The reason for K2 displaying one table as a AutoGuid and the other as Guid could be related to the following issue. 

If you created an SQL table such as:

CREATE TABLE dbo.YourTable
(
SerialID UNIQUEIDENTIFIER PRIMARY KEY DEFAULT newsequentialid()
)

,and you create a smartobject from the table, it will display it as AutoGuid. 

Whereas, if you created a table such as:

CREATE TABLE dbo.YourTable
(
SerialID UNIQUEIDENTIFIER PRIMARY KEY DEFAULT
)

, it will display the field as Guid. The reason being that with a UniqueIdentifier, we can't autocrement like how we would for integers "identity(1,1)", so we would have to increment it by using "newsequentialid()" parameter. By adding this parameter, once we create a SmartObject, it will show that field as a AutoGuid (it takes on the role of an identity type field where a GUID will be auto generated when a record is created)

Hope this helps

Hi

that isn't the case

2 tables dfifferent databases have same properties

PK, uniqueidentifier, not null

(NewID())

Hi Braddo

I faced the same issue and found it to be a case of the service account lacking permissions in SQL.

K2 was unable to recognise that there was defaults applied against the column because it was unable to fully inspect the definitions.

-Kane