The issue is due to the @[email protected]
function being called. The "aslist(@sqllist9connection,sql)@)" function will cause the data to be stored in separate rows, instead of a single row.
Our testing and analysis showed that Portal’s behavior regarding this defect is flawless and working as it is expected to. Let us explain.
Let’s imagine two scenarios where we need to return values from a database as a list:
a) The user has 3 values delimited by a comma “,”. We have a single row having:
1. “A1, A2, A3”
b) The user has 3 values in 3 separate rows. Row#3 has values separated by a comma (a legitimate character) with no delimitation intended. So, we have multiple rows having
3. C, D
If we applied Data Maker’s behavior to scenario (a), then we will have a drop down list with:
And if we implemented Data Maker’s behavior to scenario (b), then we will end up with:
However, here in scenario (b), the user expects the drop-down list to be:
• C, D
With all that explained, we suggest you extract the values you need from the database while having them stored in separate rows rather than being delimited with a comma.