My follow up question is, who is setting the "ACRE" or "EACH" values? Does the procedure populate the list, then the user selects it, or is something else happening?

You don't have "append choices to lookup results" selected, so if the lookup is working correctly it is going to wipe out those values and they won't be able to pick them anyway.

The Stored Procedure is pre-populated it like stated.

It does look to work as intended for that:

Here is the table pre-populated from my stored procedure.  When selected the drop down, all of the options are available for the user to select a different value.

Here's a section of the results from the stored procedure within SQL Studio:

The reason I asked is that I needed to know if the Stored Procedure was providing a list of values, or one specific value, because it makes a big difference in the form's behavior.

I don't really see any reason why the values would not be saved. Can you try the following to help narrow things down?

1. Start a new submission
2. After the data is populated, change one of the drop downs manually.
3. Submit the form
4. See if it saved the value you changed manually

The results will help determine where things are going wrong.

I re-ran and manually selected another option for the 2 Step Hydroseeding as seen above.

It still is not passing the MatUnit value through to the Workflow.

Here is the Form submitted.

The form when submitted is not holding the values as well.

I think at this point I will delete and recreate the field and see if that helps.

Let me know if that helps. I'm honestly stumped. Do you by any chance have field rules that hide that column under certain conditions?

Sorry I should have shown the correct part of the submitted form.  

And yes it does:

The condition should ignore values if the field is hidden.  And it should be shown when the value is Material which it does.

I have tested as well with changing the Ignore to Save hidden data and it still has the same result.