It’s should always be just 1 “Values”, so use the first.
The table “items” should always have the headers: description, quantity, unit-price, line-amount
I personally find this terrible advice since the generated data types are just superior.
The line items do work with the generated data types and don’t require all of the late binding you have to do with your workaround with them off.
You are likely using the object wrong. Is your table called ‘Items’ in the receipt.
Its super easy to iterate over the tables returned in a generated data object, there is just something small you have got wrong or are missing.
Data type ON only works with the Out-Of-The-Box models anyway?
Most of the time you will make your own DU Project and start with an OOTB model where you add and remove fields and retrain on your own data.
The Published model doesn’t support getting the generated data types.
OOTB is mostly useful for making a prototype for your process.
Thats not been my experience at all. I always used modifed models with custom fields. It always made custom data types that reflected the fields I specified.
If its not working for you its either a bug or a misunderstanding. Perhaps show the issue?