InfoPath Dev

After deleting a repeating section on my InfoPath form and submitting the form back to the site, the published column still contains all the data that used to exist in the form.  The column is created by a double eval based on the repeating section. The fields in the form display correctly, but after saving the form the XML file itself still contains the old data. When the form is opened again the repeating section is gone and now the XML modifies itself somewhat but there is still residual data.

 What could cause this? I have about 3 double evals that feed a master double eval (repeating sections within a repeating section).

Here is an example template that demonstrates the problem. Enter values into the fields highlighted green, adding as many fields, field groups or primary groups as you like. You'll note that all field values are aggregated into large double eval expressions.

The problem is that the high level double evals do not update when an entire repeating section is deleted. How can this be corrected?

Attached is a sample XML file that can be used to preview the form. Delete the "Primary Repeater Section 2" group and see that the "Repeater Aggregate Stage 3" field does not update.

 Yeah, I see what you are saying, The formula is not reevaluating. If you then change a value in one of the remaining nodes, it reevaluates. But I tried putting the primary repeating group into a parent group, so it wasn't directly under the root, and it seems to work then. Can you try that?

Hilary; not sure I fully catch your drift - would you mind uploading a modified version of the template? I greatly appreciate your help.

I tried creating another group under the root and then moved the "Primary_Repeater" group into it, but it didn't seem to make a difference. I may not have understood your instructions. Also, if I modify the node structure too heavily it no longer loads the sample data. I have production forms that have this problem (yikes!!) and I can't risk losing the data. Clearly poor design oversight on my behalf... but I'm not sure I should have even gotten to this point with InfoPath. Active Server Pages next time most likely...

 It won't work with your sample data with this change - and it will definitely cause issues with existing forms, unfortunately. I'm attaching a screenshot showing the change I tried - I then filled out the form w/out using your sample data and removing a Primary_Repeater updated as anticipated. I'm not sure offhand how to get around this - I tried adding a field to the form that counted instances of Primary_Repeater but if that group was a child of the root node, it also didn't update when it was deleted.

What I observed is that removing all the secondary repeater groups before removing the primary repeater group seems to fix the issue. It's annoying, but it's a functional workaround... Thanks for taking time to look into this Hilary! I always appreciate your help.