Thank you for your patience with my many questions.
I would like to define a column's possible values for front-end editing based on the logged-in user.
My wp_users are teachers entering data about their students. I have a "students" table where they can enter their students' names and dates of birth. This is set up so that users can only see and edit their own data.
I have a "report attendance" table where they can enter attendance for each of the students that they entered in the "students" table. This is also set up so that users can only see and edit their own data.
The "report attendance" table has a column for each month of the year where the user enters the total attendance days for each student for each month. All of the students created in the "students" table are displayed to the user. This works fine for a single year, but I will need to create a separate "report attendance" table for each school year.
I would like to allow new records to be added to the same "report attendance" table for the multiple years in the same table. If I allow users to create a new record, they need to be able to specify the year and the student for that record. I need to have a drop down menu of choices which shows only those previously entered by that user in the "students" table.
Is there any way to do this?
From what I've read in the documentation, it seems that I cannot have a dynamic drop-down of possible values for a front-end editable form, but would need to define static values for this. I could "create from column values", but would have to do this any time new students are added, which is not ideal.
I just found your response to another ticket and see that this will be available in version 2.0. I guess I'll have to just have separate tables for each year for now. I'll be happy to combine the data into a single table when 2.0 is available. :)
Yes you are correct. This feature will be available from the version 2.0 for Server-side processing tables (MySQL with Server-side processing feature enabled and Manual tables). For now it is possible just for Non-Server-side processing tables. Version 2.0 is currently in the development stage.
Thank you for your patience with my many questions.
I would like to define a column's possible values for front-end editing based on the logged-in user.
My wp_users are teachers entering data about their students. I have a "students" table where they can enter their students' names and dates of birth. This is set up so that users can only see and edit their own data.
I have a "report attendance" table where they can enter attendance for each of the students that they entered in the "students" table. This is also set up so that users can only see and edit their own data.
The "report attendance" table has a column for each month of the year where the user enters the total attendance days for each student for each month. All of the students created in the "students" table are displayed to the user. This works fine for a single year, but I will need to create a separate "report attendance" table for each school year.
I would like to allow new records to be added to the same "report attendance" table for the multiple years in the same table. If I allow users to create a new record, they need to be able to specify the year and the student for that record. I need to have a drop down menu of choices which shows only those previously entered by that user in the "students" table.
Is there any way to do this?
From what I've read in the documentation, it seems that I cannot have a dynamic drop-down of possible values for a front-end editable form, but would need to define static values for this. I could "create from column values", but would have to do this any time new students are added, which is not ideal.
Thanks again for your time.
I just found your response to another ticket and see that this will be available in version 2.0. I guess I'll have to just have separate tables for each year for now. I'll be happy to combine the data into a single table when 2.0 is available. :)
Hi sandiknowles,
Thank you for the purchase.
Yes you are correct. This feature will be available from the version 2.0 for Server-side processing tables (MySQL with Server-side processing feature enabled and Manual tables). For now it is possible just for Non-Server-side processing tables. Version 2.0 is currently in the development stage.