InfoPath Dev

I have an IP form library that was developed years ago as a 2010 filler form. It is plan and simple form with standard input. The SPO column in question receives input from a drop-down that is fed via a SP list data connection. It worked flawlessly for years. We recently migrated from SP2016 onprem to SharePoint Online. Several months prior to the migration the form was reconfigured as a web browser form and continued to work without any issue. It wasn't until after the migration to SharePoint Online that the column (single line of text) stopped pulling in the field from the form. I currently have 1500+ documents in the library. New documents have to be approved before they are published for all to see. One option is to rework the form in InfoPath 2013 and add a new column to replace the column no longer receiving input. I can then copy the contents of the old column into the new column. However, doing so will reset all of the old documents back to a pending state where they would all need to be approved again. One significant reason I would rather not go that route are the alerts. I have several users that have alerts setup on this library and I don't want 1500+ alerts fired off to those users. My hope is someone has seen this issue and it's an easy fix. I appreciate any help.

Is there only one promoted property affected? Are there other promoted properties in the form? What tool did you use to migrate with? I'm wondering if the promoted property itself is the issue - I suppose you could try republishing the template as is to the library.... You might also check the library settings - any chance there are multiple instances of the column? I've seen that happen before.... and then the view has the "wrong" column in it.

Hi Hilary, there are a total of 8 promoted fields. The problem is with only one. I have republished the form multiple times to include changing the field's control type from a dropdown list to single line of text but the input still doesn't populate.

Yuck. I guess the one thing I might try is to removed the promoted property, publish, re-add the promoted property, republish. Then just open one existing XML and see if the promoted property is populated - generally you just have to "touch" the XML to get the property to update (as long as it is associated with a field that is in the XML you open). If that works, you should be able to just copy all the files from the library to get the data to populate - hopefully that won't fire any alerts. Sadly, the Windows Explorer option is no longer available, but you might be able to make it work in Edge set to use IE compatibility. Or maybe you could use PowerShell to download all the files in the library - again, you can test by just downloading a few and see if the data populates.... SharePoint designer may also be an option for copying the files.

Hilary, thanks for the suggestions. I will try to implement your recommendations.