At this stage I would only be guessing and my guess is that the data source is not being populated for some reason.
First point of call is server side (Server Connect) database query and make sure that you have not applied any filters. Also make sure that you save your server side actions. The latter is usually part of the problems that I encounter.
Second point of call is client side (App Connect) , making sure that the Server Connect has received the contents from the query. This can be done by clicking anywhere in your document until you see the Insert Binding button. I usually go to Code view to do this.
I finally figured out why my table rows were not displaying. You have to be careful how you name the query’s condition parameter… I was including a hyphen to separate the filename’s prefix from the rest of the filename which prevented the query from pulling the records – thus preventing them from displaying.
For example: all my image filenames are prefixed with 3 letters and a ‘-’. E.g., ‘abs-filename.jpg’ where the ‘abs’ prefix is used to sort all the images in my images folder into categories (abs is short for abstract). So in my query I was using "SELECT * FROM gallery_items WHERE Description LIKE ‘abs-’ " — getting rid of the ‘-’ in the query statement allowed the rows to display.
Thank you my friend for your persistent help. Hopefully I’ll get to a point where I can reciprocate and be of some help to others starting out with Wappler.
Here’s a question (just out of curiosity):
What is the difference building a dynamic table using the table component where you have to remove all but one row from the template table, and then use the Make Repeat Children function to repeat the rows, and then touch each column to link the data with your dB’s columns & cells, then add columns that the template table didn’t, and then rename the headers… when the Bootstrap 4 Table Generator does all that with two clicks?
What is the difference between the two outcomes and why use one method rather the other?
Randy, I think you have already explained the difference, the Table Generator (and the Form Generator) makes things so much easier and, more importantly, quicker. Don’t you love it?
As a side note, I would not set the query filter (condition parameter) on the server side (Server Connect) but on the client side (App Connect) by using Data View which in turn is based on Server Connect To illustrate