That's fine. I assume I should be looking at any of the decimals?
Since I don't believe I mentioned it yet, here is my obligatory: Please ensure Connect is up to date. Current version is 3.19.116. If you install from the Microsoft Store, it updates automatically. An out of date Connect can result in many unforeseen issues.
In the case of the decimals causing the issue... there really isn't a lot going on there. Can you clear the "bind::esri:fieldType" column and see if that has any effect?
Setting this for most values is redundant anyways since Connect automatically maps the "type" to a predefined "esri:fieldType". Generally speaking, most people only need to use the "null" fieldType.
Here is a list of automatic conversions:
'type' column
| Esri fieldType automatically applied
|
text, select_one, select_multiple, calculate, hidden, email, start, end, deviceid, barcode, note | Text |
integer | Integer |
date, dateTime | Date |
decimal | Double |
geopoint, geoshape, geotrace | Geometry (point, line, polygon respectively) |
file, image, audio | Attachment |
If your issue persists after that, make a new survey and add in a single question type of "decimal" and see if that works on its own. This is essentially what you have in your main survey. If this works, something funky is going on. If this doesn't work, contact Esri Support and log a bug.
BTW, "Package" is a reserved field, so you should look at changing it as that can cause unforeseen issues.
Also, notes aren't added to the Feature Layer if you don't give them a "name". You can remove this note's "name" and "null" parameter for the same effect: