Page 1 of 2
Grey screen when data mapping to a select element
Posted: Wed Aug 01, 2012 3:11 pm
by ghuisintveld
In my project Client Online (already shared with support), I have a REST datasource with an array connected to a select element. When the page is loaded, the whole screen turns grey. I've tried mapping it to a grid which works fine.
Grey screen when data mapping to a select element
Posted: Wed Aug 01, 2012 4:21 pm
by maxkatz
How do I get to that page? What Pin should I enter to log in?
Grey screen when data mapping to a select element
Posted: Wed Aug 01, 2012 5:09 pm
by ghuisintveld
O pardon, the pin is 12345. It's the first page that opens, you'll see.
Grey screen when data mapping to a select element
Posted: Wed Aug 01, 2012 5:56 pm
by maxkatz
And it works with Grid but fails with Select menu?
Grey screen when data mapping to a select element
Posted: Thu Aug 02, 2012 11:28 am
by ghuisintveld
Exactly! I've now implemented both. First login and see the grid being built up correctly (2 rows). Then click a different page in the bottom menu. Then click on Home again. You will be redirected to Home2. This page contains the select and will be grey (or white).
Grey screen when data mapping to a select element
Posted: Thu Aug 02, 2012 6:22 pm
by maxkatz
Add a dummy value to the list -- it should work then. We are planning to fix this on Monday.
Grey screen when data mapping to a select element
Posted: Mon Aug 06, 2012 2:42 pm
by ghuisintveld
This works, again great support thanks!
Grey screen when data mapping to a select element
Posted: Mon Aug 06, 2012 3:26 pm
by maxkatz
We just released an update, it should work without the dummy value.
Grey screen when data mapping to a select element
Posted: Mon Aug 06, 2012 7:19 pm
by ghuisintveld
Sorry but the release doesn't fix the problem, I now see 1 value in a grey screen. The dummy value however works fine and solves the problem for me!
Grey screen when data mapping to a select element
Posted: Mon Aug 06, 2012 7:25 pm
by maxkatz
Sorry, my bad. It's not fixed yet. So continue using the workaround for now.