Hi,
I use guid as my primary key.
Insert command don't create new guid when i insert record.

Is it possible to customize guid data filelds??

Thanks

 Igor

Hi Igor,

Dynamic Data treats Primary Keys in a special way (for example, hiding them from the autogenerated pages). Having an autogenerated GUID actually falls within the realm of SQL Server. You can achieve this by specifying that your GUID column should have a default value and that default value should be ther result of evaluating the newid() function (look at Example B here for more info: http://msdn2.microsoft.com/en-us/library/ms190348.aspx).

Hi Marcin,

Thanks for the quick answer.
Best Regards

Igor

I still have the same problem after adding newid() function.
I seems that linq to sql always insert 00000000-0000-0000-0000-000000000000 value in db.

Any ideas?

Thanks

One solution is to add newid() function in db and than change column property isDbGenerated:=True in linq to sql generated classes

<Column(Storage:="_CustomerFaxTypeID", DbType:="UniqueIdentifier NOT NULL", IsPrimaryKey:=True, IsDbGenerated:=True)> _

Problem is that i must change that property every time when i generate linq to sql classes.

Is there any other solution??

Igor

Sorry, I forgot to mention that detail.

You can set that property using the Linq to SQL designer and then it will automatically be included in the autogenerated code (unless you completely remove a table from your model and drag it in again - but this is an issue with Linq to SQL and not Dynamic Data):

1. Open your Linq to SQL model
2. Right-click on your GUID property and select Properties
3. In the Properties Editor in the Data Section change the value of the "Auto Generated Value" property to true.

I have a similar problem using an auto-incrementing numeric as a primary key.

When adding a new item using the default template it creates a textbox for the ID.

Hiding the column is no good as it will complain that the column is required.

Whatever number you type in it will save the next available ID anyway, unless you type an existing ID, in which case it will complain the ID already exists.

 IsDbGenerated is set to true.

Is there an easy, or even a dirty way around this?

Hide the ID column and pass the max possible ID every time somehow?

First off I'm assuming that the field in your database is set as an identity column? If it is an identity column and a primary key then we will hide the field and it will automatically get incremented as each new row is put in. If you modified the database after you created your Linq Classes you probably should delete the table from the Linq designer and drag it back onto the designer from the database. On my machine a working table with an identity primary key looks like this:

 Auto Generated Value: true

Auto-Sync: OnIsert

Primary Key: true

 Note if we do not show a column and you want to add it you can always for the column to show by adding it manually:

<asp:DynamicField DataField="fieldname" />

 ...Scott

Note that if you have a DynamicDetailsView, you are likely using the old December build, as this control no longer exists.  If possible, please give a try to the new build.

thanks,
David

I'm having a similar problem in SP1 beta and 3.5 sp1 beta...I don't see the options of autogenerate and I'm using an Entity Data Model

Does anyone know how to let the dynamic data rely on the SQL generated GUID for the primary key field?

were you ever able to get this fixed? I'm having the same issue with Entity Data Model, but I don't see the options they are referring to.

Entity Framework does not have the ability to tell Dynamic Data whether a column is generated, so by default we always assume it's not.  To work around this, you can put a ScaffoldColumn(false) attribute on the property, e.g.

[MetadataType(typeof(Products_MD))]   

partial class Products {    }   

partial class Products_MD {       

   [ScaffoldColumn(false)]       

   public object ProductID { get; set; }   

}
 

So here is the working solution for this issue.

 Using the same namespace as your data model create a class.

 Then create your partial class of the table you wish to use a SQL server set newid() guid.

Here is a copy of the class I created.

using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.ComponentModel.DataAnnotations;
 

     partial class ClientInformation_MD
     {
          [Scaffold(false)]
          public object ClientGUID { get; set; }
     }

I've been using aspnerd's solution since all my entities have autogenerated (numberic identity) keys and I don't want any of them in my forms. However it seems really wrong to have to break out a partial class every time we want to skip the scaffolding of an autogenerated key which should basically never be scaffolded anyway doesn't it? Is there any better way of doing this?