InfoPath Dev

Hi,

I am trying to create three infopath forms ( ex : Project, Purchase Requisitions, Purchase Orders)

Requirement here is :

step 1: First user will create Project

step 2: User create purchase Requisitons against project ( here i am providing dropdown box and populating all projects with data connection)

stpe 3: user create purchase order against purchase requestion ( here i am providing dropdown box and populating all purchase requisitons).

Query 1: When the user done step 2 and see the form library view of purchase requistions then project name is displaying as number (ID value). Here i want to show project name. if user changes the project name in the first form it has to change in the second form also automatically. ( this can be achievied using two custom lists but i want same with form libraries).

Query 2: How to maintain unique value for xml file name: when the user submits the project, i am assignging project name to file name. because project name should be unique here. But the problem is, i need to provide the functionality to edit project name but if i change project name, it is creating new record.

Could you please help me regarding the above two problems. 

Regards,

KV

Query 1:

The ID value is most likely the ProjectID (which is guaranteed to be unique). There's no guarantee that the ProjectName will be unique so SharePoint cannot have a look up relationship based on that. You could add another field in the form to store the ProjectName, and have rules in the form to obtain the ProjectName based on the ID. If you make this field a promoted property, then you'll have a Project Name column and can hide the ProjectID column. 

Query 2:

The InfoPath form determines the filename on first submit. You can set the data connection to overwrite if that filename already exists in the form library. But the submit options in InfoPath don't offer anything that would allow you to overwrite an existing XML form that now has a different name.

I suggest you name the forms with something unchanging and unique, if you expect the ProjectName to be changing. Otherwise you'll end up with new records.

Another option would be to find a way (Workflow?) to tell SharePoint to delete the previous document, but that seems very complex.