I understand that you can set entries to be seen by the editing user only. What I'd like to clarify is when a user creates related relational tables, that the selection will only show their created entries. I trust this is not too confusing. The attachment should make it clearer (I hope?)
Essentially I have a number of users who have different customers, who will create orders/invoices. Each user will only be able to see their customer and order entries, so that when the user selects the customer column in his order, he will only have a choice of his customers
Tables can only be created by administrators, in back-end. So, your users (Rocky, Fran, Doug, John, Mary) need to be admin users if you intend to create tables with those users.
If they are regular users, this could still work. You would create the customer table, where you'd select "userid" as the User ID Column for editing, when you enable "Users see and edit only own data".
When this table is edited, or a new value is added through front-end, it will store the data of the currently logged-in user in the UserID column.
Order table would also have to be populated in a similar way.
I'm not sure I understand the drop-down section, though. Each drop-down (filter) is associated to the column. So, you would be able to filter per column.
Thank you for the quick response. Let me try to clarify.
Since we will be using one table for customers, users will enter their own customers, which is linked to their User-Id
When the user adds a new entry (linked to their User-Id) to the orders table, they will select a customer. That selection must only include (be filtered) to show the customers they created.
So in real terms the customer select field is based on a filtered view of their customers
In order for users to see only the customers they've created, you need to enable "Users see and edit only own data" and use "Foreign Key" feature to link the customers table with the orders table.
So, in the Orders table, you'd configure a foreign key linked to the customers table. When users try to select a customer from the remote table, they will only be able to see the ones they've entered.
There are no issues with this, since you're opening the tickets using your purchase code. If you need to delete one of these profiles, please reach out to Ticksy at this link, and ask them how a profile can be deleted. I honestly wouldn't know
Hi
I understand that you can set entries to be seen by the editing user only. What I'd like to clarify is when a user creates related relational tables, that the selection will only show their created entries. I trust this is not too confusing. The attachment should make it clearer (I hope?)
Essentially I have a number of users who have different customers, who will create orders/invoices. Each user will only be able to see their customer and order entries, so that when the user selects the customer column in his order, he will only have a choice of his customers
Hello Rocky
Thank you for your interest in our plugin.
Tables can only be created by administrators, in back-end. So, your users (Rocky, Fran, Doug, John, Mary) need to be admin users if you intend to create tables with those users.
If they are regular users, this could still work. You would create the customer table, where you'd select "userid" as the User ID Column for editing, when you enable "Users see and edit only own data".
When this table is edited, or a new value is added through front-end, it will store the data of the currently logged-in user in the UserID column.
Order table would also have to be populated in a similar way.
I'm not sure I understand the drop-down section, though. Each drop-down (filter) is associated to the column. So, you would be able to filter per column.
Kind Regards,
Aleksandar Vuković
[email protected]
Rate my support
wpDataTables: FAQ | Facebook | Twitter | Instagram | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Instagram | Amelia demo sites | Docs | Discord Community
You can try wpDataTables add-ons before purchasing on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables
Thank you for the quick response. Let me try to clarify.
Since we will be using one table for customers, users will enter their own customers, which is linked to their User-Id
When the user adds a new entry (linked to their User-Id) to the orders table, they will select a customer. That selection must only include (be filtered) to show the customers they created.
So in real terms the customer select field is based on a filtered view of their customers
Trust this helps
Hello again Rocky
In order for users to see only the customers they've created, you need to enable "Users see and edit only own data" and use "Foreign Key" feature to link the customers table with the orders table.
So, in the Orders table, you'd configure a foreign key linked to the customers table. When users try to select a customer from the remote table, they will only be able to see the ones they've entered.
Kind Regards,
Aleksandar Vuković
[email protected]
Rate my support
wpDataTables: FAQ | Facebook | Twitter | Instagram | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Instagram | Amelia demo sites | Docs | Discord Community
You can try wpDataTables add-ons before purchasing on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables
Thank you. I will experiment on the sandbox
You're welcome Rocky
If you have any other questions please feel free to ask
Kind Regards,
Aleksandar Vuković
[email protected]
Rate my support
wpDataTables: FAQ | Facebook | Twitter | Instagram | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Instagram | Amelia demo sites | Docs | Discord Community
You can try wpDataTables add-ons before purchasing on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables
Hey Rocky
I don't know if you can do that.
There are no issues with this, since you're opening the tickets using your purchase code. If you need to delete one of these profiles, please reach out to Ticksy at this link, and ask them how a profile can be deleted. I honestly wouldn't know
Kind Regards,
Aleksandar Vuković
[email protected]
Rate my support
wpDataTables: FAQ | Facebook | Twitter | Instagram | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Instagram | Amelia demo sites | Docs | Discord Community
You can try wpDataTables add-ons before purchasing on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables