Hi @pradhansb,
Thanks for your below suggestion.
The challenge with what you suggest is that a table can exist of any type of data, and without following the logic of WordPress hierarchy of data (Custom Post type, Custom Field, etc) we would have no knowledge what data constitutes a field with values and what other ‘field’ to sync it to.
So that setup is too broad for this plugin I’m affraid.
Having said that, as long as the data is of these types it should work in the new version:
Post meta, term meta, user meta, comment meta or users.
Want to try the beta? If so send me a Direct message.
Here is a biggy pjfc:
Open table in db, any table.
Open second table.
Map selected fields of Table 1 into Table 2.
An example. I am using Bookly which is an appointment plugin. It keeps its own table of bookly customers. On the backend, you can opt to create a wp account when entering the data.
But, you can also register a user independent of Bookly but it does NOT create a bookly customer.
I would love it to. This way I could use an independent registration plugin up front.
Thanks for your consideration.
Pradhan