We're Moving to a New Support Platform – Starting June 1st!
We’re excited to let you know that starting June 1st, we’ll be transitioning to a new support system that will be available directly on our product websites – Amelia, wpDataTables, and Report Builder. In fact, the new support platform is already live for Amelia and wpDataTables, and we encourage you to reach out to us there.
You'll always be able to reach us through a widget in the bottom right corner of each website, where you can ask questions, report issues, or simply get assistance.
While we still do not offer live support, a new advanced, AI-powered assistant, trained on our documentation, use cases, and real conversations with our team, is there to help with basic to intermediate questions in no time.
We're doing our best to make this transition smooth and hassle-free. After June 1st, this current support website will redirect you to the new "Contact Us" pages on our product sites.
Thanks for your continued support and trust – we’re excited to bring you an even better support experience!
How can I use values from another wpdatatable for filtering?
If I define another table in "Possible values for column", this values are not displayed in a table filter. Instead "Read from table on page load" values are displayed.
Hi Miroslav
Please check if the origin headers are the same for both tables - they should be different.
If you go to the column settings in the top left corner you will see origin header.
If "store value" or "display value" header is the same as in the table you want to configure the foreign key it will not function properly.
Do let us know if you need any further assistance.
Thank you for your response.
The headrs are different. See screenshot below.
What values are displayed in the filter if another table is set for possible column values?
Are this valus from other table or the values stored already in the table?
Hi Miroslav
By default you should be able to see the values from the foreign key column. The column name from the original table should be different from the column name of the foreign key table as well to avoid conflicts.