Found the problem.
It doesn't like the columns that you have named as "#. Question Text" - which I assume you were using to reflect questions/responses, with the question text as the column header. The formatting of those, with the period (.) in it appear to break during the import from Excel.
You'll need to revise those column headers to get the data into the app. You can generalize the column names, and use a second table to map the generic names to the question text, like I have below. Alternatively, questions can/should be normalized into their own table, as a lookup to the response, and a value-pairing of question/response.
Isolated the columns which came into the app, from original table.
Confirmed in test app, using data source.
Renamed the missing columns to a simpler pattern.
Confirmed those columns now appear in app, via static data.
Example table that maps the question text, to the generic column name.
It's funny, because you can declare column headers like that, but I think it's a limitation/bug from Excel.
ClearCollect(
colTest,
{
'abc123': "abc123",
'abc 123': "abc 123",
'abc . 123': "abc . 123",
'abc # 123': "abc # 123"
}
)
Let me know if you have any other questions.
