Hi George,

Actually we have a knowledge base about retrieving identity, probably you can use it also, you can browse it in http://support.intersoftpt.com/KBArticle.aspx?aid=207 or http://support.intersoftpt.com/KBArticle.aspx?aid=227.

Hope this helps.

Best Regards,

Gordon Tumewu

Gordon,

My issue is not in retrieving the GUID.  It is in INSERTING the GUID.  I will post a video for you.

Thanks

You can find the video Here

Hi George,

It's true, I noticed that your issue is in inserting, the issue that you have because that the ID column cannot be null, that's why I point to the knowledge base, if you check the knowledge base contain step by step to handle the inserting problem if the ID cannot be null. I think it's similliar with your issue.

Best Regards,

Gordon Tumewu

Gordon, the insert stored proc, does not require the id.  The ID is passed internally. Here it is:

[dbo].[sp_Business_Insert]
(
 
 @BusinessName nvarchar(100),
 @Address1 nvarchar(100),
 @Address2 nvarchar(50),
 @City nvarchar(50),
 @State nvarchar(20),
 @PostalCode nvarchar(20),
 @Country nvarchar(30),
 @ProfessionalID1 nvarchar(50),
 @ProfessionalID2 nvarchar(50),
 @ProfessionalID3 nvarchar(50),
 @StatusID tinyint,
 @AdminFirstName nvarchar(20),
 @AdminLastName nvarchar(20),
 @AdminPhone nvarchar(20),
 @AdminPhoneExt nvarchar(10),
 @AdminEmail nvarchar(50),
 @GName nvarchar(20)
)
AS
DECLARE @BusinessID uniqueidentifier
SET @BusinessID=NEWID()

 SET NOCOUNT OFF;
INSERT INTO [dbo].[Business] ([BusinessID], [BusinessName], [Address1], [Address2], [City], [State], [PostalCode], [Country], [ProfessionalID1], [ProfessionalID2], [ProfessionalID3], [StatusID], [AdminFirstName], [AdminLastName], [AdminPhone], [AdminPhoneExt], [AdminEmail], [GName]) VALUES
(@BusinessID, @BusinessName, @Address1, @Address2, @City, @State, @PostalCode, @Country, @ProfessionalID1, @ProfessionalID2, @ProfessionalID3, @StatusID, @AdminFirstName, @AdminLastName, @AdminPhone, @AdminPhoneExt, @AdminEmail, @GName);
 
SELECT BusinessID, BusinessName, Address1, Address2, City, State, PostalCode, Country, ProfessionalID1, ProfessionalID2, ProfessionalID3, StatusID, AdminFirstName, AdminLastName, AdminPhone, AdminPhoneExt, AdminEmail, GName FROM ArcBusiness WHERE (BusinessID = @BusinessID)

George, in normal GUID case, the Grid should be able to insert the row successfully without additional code. However, your case is a bit different since the GUID is assigned in the backend, and not from front/middle layer.

Fortunately, WebGrid has a solution for your scenario which is very similar to the solutions in the KB article that Gordon provided. In short, you need to pass the GUID from backend into datasource level which involves two phases:

1. Define an InputOutput parameter in the InsertParameters of your ISDataSourceTable definition.
   Example:
   

   <InsertParameters>
               <asp:Parameter Direction="InputOutput" Name="BusinessID" Type="Object" />
               ... 

2. Customize/extend your DoInsert method which retrieve the GUID that assigned in the backend, and pass it back to the InputOutput parameter. 
   Example:
   

   DataObjectMethodAttribute(DataObjectMethodType.Insert, true)]
   public int DoInsert(ref System.Guid BusinessID, ...)
   {
       // your insert call to SP
       objecet returnValue = DAL.InvokeYourInsertSP(params);
       // assign the returnValue, which should be the GUID value from your SP call
       BusinessID = returnValue;
   }

The above code assumes that your SP should return the GUID value properly, as in the case of Northwind sample where it returns the identity of the OrderId.

When an InputOutput parameter (ref) is assigned back from DoInsert method, WebGrid automatically detects the new value and assign it to the datasource and UI. 

Hope this helps,
James.