I’m curious as to whether there’s a reason to use inner-text instead of insert a binding. When using the list generator, all the cells use the inner-text attribute but it means you don’t see anything when designing the page. So I tend to remove that and insert a binding instead. Is there any reason not to do this?
eg.
<td dmx-text="SiteID"></td>
versus
<td>{{SiteID}}</td>
The latter makes it much easier to work with.
The only downside of using:
Could be:
And layout jumping in some rare cases when loading large data sets.
I wondered if that might be the case. Does the inner-text method avoid this, then?
Yes 
I have to change almost all of my inner-text to bindings in tables. If you have a cell with a null value it will pick up a random binding from another record. Changing to <td>{{SiteID}}</td> also gives me more flexibility to add dynamic links etc.
I see no advantage to using inner-text personally.
Yep, I’m similar to you, Brad. But I do accept the FOUC scenario although it’s not been a problem for me… so far!
Not sure what you mean Brad. Probably you are not using a key for your repeat children region.
For example, I find it especially more so for date data but also happens with some strings, if I have a table that has a column of dates and some rows don’t have a date it will populate the cell from either the row above or row below.
Happens pretty much all of the time. Changing from inner-text to a binding solves it 100% of the time.
That’s very strange. Sounds like something not quite right with the query.
As I suggested:
Not sure what you mean by using a key? They are just simple paged queries displayed on the page by using the table generator. Nothing special about them.
Brad, there is an unique KEY option available for your repeat children region. Most probably you have not selected anything for its value. So that’s the reason null values don’t update on data refresh…
Where in the UI do you set it? I would love to know if there is something I have been doing wrong all this time. Thanks
Well it’s in App Connect panel Select your repeat children region and it will appear in the properties.
I see it now. I will definitely give that a try. Thank you.
Maybe that should be added to the table generator UI. I would never have thought to look there for anything.
It is not a feature of the table generator, but rather it is a feature of a repeat. Two separate things.
Should it avoid it completely? I still get FOUC sometimes, even when I use inner-html (which I think should give similar results to inner-text). Is this to be expected or could something else / some problem cause it?
I think you also mentioned that using inner-text/html is faster.
Is this not the reason for putting '.default()' on any dynamic data if there was a chance that a 'null' was returned?
I suppose that would work as well. Didn’t think of that. Good idea.
Oh interesting... so .default() gives a value if the variable is null... and does it trigger in any other situation, like empty string?