I can see an easier workflow and would personally benefit with an option to create Sql Tables implementing Primary Id's with simple Integer data types instead of being limited to 30 character GUID's
There's a few reference points and assumptions within the C1 code that expects the long GUID's in Sql Tables. I would like to see more flexibility to be able to use a simple Int Data Type as Identity (which increments by 1 to ensure each row is unique) with primary key.
I see many uses and benefits of being able to set up reference tables etc with simple numeric id's as the index primary keys within application uses for C1.
See the discussion thread below for prompting me to propose this feature:
http://compositec1.codeplex.com/discussions/358931#post847245
Comments: ** Comment from web user: Nime **
There's a few reference points and assumptions within the C1 code that expects the long GUID's in Sql Tables. I would like to see more flexibility to be able to use a simple Int Data Type as Identity (which increments by 1 to ensure each row is unique) with primary key.
I see many uses and benefits of being able to set up reference tables etc with simple numeric id's as the index primary keys within application uses for C1.
See the discussion thread below for prompting me to propose this feature:
http://compositec1.codeplex.com/discussions/358931#post847245
Comments: ** Comment from web user: Nime **
This should be done!