J
JimJ
I have my Infopath form working where it will submit data to SQL Server and
the SQL server automatically provides the next sequential number (identity
column), but I then want to store that number in the form (xml) on Sharepoint
so that the number on the form is identical to the unique key value of the
purchase requisition in the SQL server database. That way when the requestor
(or someone) opens that form/document up it will then query the data out of
the SQL server based on that unique key identifier that is stored in the
form. I am also tying this to Sharepoint workflow so that I need that
special unique identifier for the document to tie it to the database data.
I wonder if anyone has some tips and/or best practices with this type of
functionality. It would seem like it should be very common for any type of
documents that need to be tracked with some solid process and be able to rely
on unique identifier, digital signatures, workflow, and a document (that may
also have attachments to it).
Thanks, Jim
the SQL server automatically provides the next sequential number (identity
column), but I then want to store that number in the form (xml) on Sharepoint
so that the number on the form is identical to the unique key value of the
purchase requisition in the SQL server database. That way when the requestor
(or someone) opens that form/document up it will then query the data out of
the SQL server based on that unique key identifier that is stored in the
form. I am also tying this to Sharepoint workflow so that I need that
special unique identifier for the document to tie it to the database data.
I wonder if anyone has some tips and/or best practices with this type of
functionality. It would seem like it should be very common for any type of
documents that need to be tracked with some solid process and be able to rely
on unique identifier, digital signatures, workflow, and a document (that may
also have attachments to it).
Thanks, Jim