Hi Ted.

Firstly, I would like to sincerely apologize for the delayed response as we have been experiencing an unusually high number of tickets. I am sorry that it has taken longer than usual to respond to your concern and your patience is highly appreciated.

-

1. Sorry to disappoint you, but when we link a source Gravity Form to output data in our connected dataTable via our Gravity add-on integration,

it is not possible to pass the Field Description, our table will only pull the Field Name and Field Type from the source Form.

You can suggest this as a future option, though.

Please feel free to search on our suggestions page, 

 to see if someone may be already suggested this feature. If you can't see it, feel free to add your suggestion there,  and as more people vote, the feature will move higher on the priority list.

You can certainly follow our changeLog page if you'd like ( it is also available in the plugin dashboard), where we state any changes/new features/bug fixes during updates;

and our newsletter, so you're informed about new features, bug fixes, freebies, etc.

2. In regards to a hidden field showing in our PopUp Form,  

could i take a closer look at the back-end of this table in question?

I can't seem to reproduce this issue on my end.

We have this dummy Gravity Form and if i add a hidden field, let's say to store the currently logged user's UserName,  it auto-populates with the username of the person who submits the field,

but it does not show in the Editing Modal if we add a new row.

I also tried with a hidden textual auto-populate field, but still can't get it to show in the Editing Modal of our connected Table.

If you could show me some screenshots or a Video to see how this particular hidden field is configured in the source Gravity Form, and how it looks in the Editing Modal?

We can devise an easy custom CSS for you to hide it, as well, i suppose.

If we can see the back-end of the table.

Please provide me a temporary WP-admin (administrator) user for your site where this happens, so we could log in and take a look ‘from the inside’ as that’s the most efficient way to see and resolve the issue. 

We do not interfere with any data or anything else except for the plugin (in case that’s a production version of the site), and of course, we do not provide login data to third parties. 

You can write credentials here just check PRIVATE Reply so nobody can see them except us.

And point me to the table ID, please.

Hi, Ted.

I am sorry to see that you had to go through this trouble to make the use-case work,

but happy to see that you found a working solution.

We will be here, let us know if you encounter any other issues and we will do our best to advise.

We are still unable to reproduce this initial issue with the hidden fields,

so sadly we can't say exactly what causes it on your site.

Thank you.