SQL Database Integration

Re: SQLServer uniqueid columns

Anonymous — Sat, 26 Feb 2005 20:43:05 GMT

I have the same problem - but I don't know how to modify the automatically-created schema. If I extract the Infopath document as a collection of files and then modify the relevant XSD file so that the attribute is 'optional' and then reopen the Infopath document in design mode, the uniqueidentifier field still shows as a mandatory item and I am unable to change the mandatory field setting.

How can I modify an automatically-created connection so that I can submit a record without a GUID? I tried changing database settings so that the GUID is not a primary key and can be null, but that causes too many problems with DB relationships. There must be a better way! This one puzzles me because I have Googled for it and found very little - just people suggesting to use a made-up GUID instead of the built in SQL type. It seems like this should be a really common problem; unless I'm misconstruing something altogether...

Re: SQLServer uniqueid columns

Greg Collins — Tue, 05 Oct 2004 20:17:10 GMT

You should be able to hack the schema created for your database connection and change the field to optional.

If you ever update your data connection you will need to do this again.

Greg Collins [InfoPath MVP]

SQLServer uniqueid columns

Anonymous — Mon, 04 Oct 2004 21:01:17 GMT

I am using INFOPATH to submit to a SQL database.
I have a 1 to many relationship, where the PK of the child table
is a uniqueidentifier in one of the PK columns named SEQ which is defaulted to 'NEWID()' at the DB side.

Question is there any way to tell infopath to allow this field to be blank. Infopath forces it to be in the datasource, and makes it required.

Tx

Matt