Hi Alan,

When you create a table linked from a JSON file/ API/ Nested JSON, these tables are not saved in our Plugin and your database in the same way as a Manual table would be.

That is why our SQL Constructor helpers are not able to find this table in your SQL database, and you won't be able to find a 'stand alone SQL table' which is linked from JSON in your Database from your DB management tool either.

We will elaborate in more details just to clarify the logic behind it :

When you create a new Manual Table via our Plugin - that creates a new stand-alone SQL Table in your Database, with its own set of columns and rows; so this table can easily be found in your database and you can make easy SQL Queries from it.

On the other hand, these other 'linked' datatable types are not saved in the database like manual tables, but instead, their data is stored in database table 'wp_wpdatatables_rows' (Just to note : wp_ is the default WP DB prefix, on your Site it could be anything else so i you wish to find that table, look for 'yourDBprefix_wpdatatables_rows').

 So, pulling data from the database via an SQL Query from a table like that is a lot more complex because this database table stores data in serialzied JSON format, not like manual tables (columns * rows).

If you manage to pull that data, in the end the last step would also be to unserialize the JSON data to make it more 'humanly readable'.

This falls under advanced/custom MySQL, and unfortunately, it will not be covered by our support.

You will have to search for custom solutions online, for example, such as this one from Stack Overflow. 

2. Now, more directly the subject about the use-case you wish to achieve, to pull some of the data from the JSON linked Table and use this data to update a Manual table :

At this time, we do not know any way to achieve something like that, we do not have any built-in solution for it, so you can only try some completely custom solution which goes outside of our Plugin's native capabilities.

We can't confirm if it can be done with some custom work either, and our developers are very busy at the moment, working on some priority tasks and fixing bugs and issues with our plugins, so they won't have the time for custom work in the near future.

Sorry that we can't be more helpful on that specific use-case.

Hi Alan,

No problem, we will do our best to see what we can advise, as much as our Support can cover.

For that use-case, I see what you mean. That is a very specific use-case which we haven't tried yet, so I will do my best to see if one of our developers finds the time soon and if they can provide any useful advice which could make your scenario easier with our Plugin, we will report back to share it with you.

This does fall under custom work, so it goes outside of our Support scope, thus we can't promise anything, but we will see what we can do.

If the devs find any better/easier way for you to do this, we will advise.

Thanks again for your patience.

We will go over the other open ticket as soon as possible, too.

Hi Alan,

Just a small follow up - I spoke with our developers about this and, unfortunately, this falls outside of the scope of our Support, it is a very custom scenario.

The only advice our devs were able to comment is that you can try to change your source data into CSV somehow, then you would be able to save it that way and make it easier ( such as you can easily import CSV data into SQL database then call SQL queries from it), but they don't have an easy advise how you can do that exactly.

You can, of course, always research online on places such as Stack Overflow or similar, to see if any other user/ or a developer who does custom work, managed to make a solution you need.

I am sorry we are unable to be more helpful on this specific matter.

Hi Alan,

I see what you mean. I was not aware of this, thank you for sharing that step with us, it is useful to know as a possible workaround idea.

For the time being, we don't have any better ways, but I hope our devs could add new/improved/easier solutions for this use-case in the future.

You're welcome, we are happy to help. If anything else comes up, as you know, don't hesitate to open new tickets.