InfoPath Dev

I've created a form for staff to order office supplies.  This form is submitted to the SharePoint forms library so a SharePoint workflow can be kick off.  I have a repeating table in the InfoPath form that allows staff to order more than one items at a time.  The Product field and Price field in this repeating table are populated from a separate SharePoint list.  Everything works great except when the Price is changed in the list, it automatically update the data in the existing form.  Is there a way I can store the Price of the product at the point of time it was submitted?

I thought about inserting into a SharePoint list but the InfoPath form will not be stored.  Furthermore, I can't kick off a workflow for multiple products in a list. Is there another way of making the Price value static after submitting the form to SharePoint?

How is the price getting automatically updated within the xml when the Price is changed in the list?

Or is the price getting updated in the xml when the form is reopened? If that's the case, then a condition such as "when price is not blank" would prevent the rule from always executing.

ErnestoM,

 I thought that would solve my problem but it didn't work.  I applied the rule to when the form is open but the price still gets updated.  Can you tell me where I am going wrong?

Yes I am using a default value on my Main Source Hilary.  I have to set a default value for it to filter the price from a SharePoint list according to what Product is selected.

That is why it gets updated when the Price changes in SharePoint.

Use rules to set the price instead. Set the rule on the Product field. When the product changes, set the price field....

Thank you so much Hilary!  Your suggestion worked.  I created a rule on the Product field if it's not blank then set the value on the Price field. 

 Thanks again!!!

Using a secondary data source as part of a default value can be very powerful if you want  the value to update every time your secondary data source changes. But it can have undesireable side effects, as you have seen -- if you don't want the value in the main data source to be updated when the secondary data source changes, better to use a rule.

You may also want to set another rule on the product field -- if it is blank, to set the price back to blank. That way if for some reason the product is set back to blank (not sure if that is a valid scenario in your form), you know there won't be a value in the price field.

Happy InfoPath-ing!