SharePoint Integration

Re: Repeating table value changing to first value when submitted

Patrick Halstead — Fri, 15 Oct 2010 06:20:31 GMT

I don't know why the export to Excel would do that.

Re: Repeating table value changing to first value when submitted

rconverse — Thu, 14 Oct 2010 21:08:11 GMT

Thanks for the reply. I did make some changes and there's a checkbox about recalculating the defaults or something that I must have checked and shouldn't have. Once I unchecked that and republished the form I was set.

Just to note, even though the field on the form changed when I reopened the form, when I exported the data to Excel, the field still retained its original values.

Re: Repeating table value changing to first value when submitted

Patrick Halstead — Wed, 06 Oct 2010 07:01:15 GMT

Hi Roger,

Sorry for the delay.

You say "all of a sudden" - is this a regression? Did it work before? If so, what did you change?

Make sure that both fields are bound to a field that is in a repeating group and not a single field. If the data is in the form (open in Notepad to confirm), and you are opening the forms via their XML, the only thing that I can think of is that someone changed the default value to auto-populate and that's overwriting it (or added an Open rule that default populates it incorrectly).

Happy sleuthing,

Repeating table value changing to first value when submitted

rconverse — Thu, 30 Sep 2010 15:51:05 GMT

Hello,

I have a form with a repeating table that all of a sudden isn't working. I have a repeating table with five or so fields and our warehouse field is a combobox. When people submit, the form the warehouse value changes back to the first value in the table when submitted.

So let's say I have ATLA chosen in the first row of the repeating table and then choose to repeat that row. I can change the warehouse combobox value in the second row of that table to CHIC, but when I submit it to the SharePoint site and then open it, both records will show ATLA as the warehouse. This occurs for all records in the repeating table and has just started to occur.

Anyone else faced this issue in the past and know the resolution?

Thanks,
Roger