Hey HPPraxis.

Thank you for your purchase.

Do you have a unique ID for each row? As you had the chance to see in our documentation, it is being used as a store value.

Please provide me a temporary WP-admin login 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 party. You can write credentials here just check Private Reply so nobody can see them except us.

Best regards.

Hello HPPraxis.

I don't believe it's a good practice to use the wdt_ID column for Foreign keys.

Please take a look at the attached screenshots. You can see that the last two in [wpdatatable id=24] don't match up with [wpdatatable id=19].

If you enable editing for a column configured as a foreign key and you choose a single-value selectbox as an editor input type, editing will work naturally, and the IDs will be stored in the column.

Unfortunately, wdt_ID is a unique auto-increment integer column, and therefore cannot  be used properly for a foreign key, since upon each new row it is adding a new value, and even if you pass the correct data for other columns it will not be recognized as a store value column, until (like you said) you add it manually.

Best regards.