I created a form in 2020 with the New Responsive Designer that uses list lookups to allow users to set the status of an item and move it forward in a process. This lookup pulls from another sharepoint list with the available status options. I have the lookup control then connected to a text field in the sharepoint list the form interacts with so that when the list item is selected it will store that selection in the list for workflows to grab.

What USED to happen is the full list lookup value was stored (example: 2;#Working). What happens NOW is you can either store the ID (example: 2) or you can store the text (example: Working). However, IF you have the lookup connected to the sharepoint field it doesn't know what to do with the text, so it just sets itself to blank and the field blanks out. If I store the number, it will pull up the correct status in the list lookup BUT this will require yet another field in the sharepoint list to translate that number to what that number means so people can interact with the form.

Is something wrong, did I adapt to a broken form function that is now working the way the creators intended? Is this a known issue that is being worked? I would like to know if I have to totally redo all my forms that work this way to get them functional again, or if this is broken and will be fixed in a future release to allow both the ID and text to be stored in the field the control is connected to.