Forum Discussion
MichaelTamoush
4 years agoQrew Captain
You could use a pipeline to create the entries in your parent table. Key Field is a text field, and every time an assignment is created, a Pipeline searches to see if that version of name and date exists. If not, create a record in the parent table with that specific string in a manually entered text field.
The child table you should be able to use the formula field in the relationship. It only fails if part of the formula is from a lookup field. If that is the case, you also make a manually entered field on the child table called 'Name and Date Manual Field'. Create a dynamic rule that upon saving the record, copies the Formula field to the manual field.
But also, I'm not quite understanding why you can't just set all the appointments in your child table, then just create a report that you filter by date or user to see the schedules?
------------------------------
Michael Tamoush
------------------------------
The child table you should be able to use the formula field in the relationship. It only fails if part of the formula is from a lookup field. If that is the case, you also make a manually entered field on the child table called 'Name and Date Manual Field'. Create a dynamic rule that upon saving the record, copies the Formula field to the manual field.
But also, I'm not quite understanding why you can't just set all the appointments in your child table, then just create a report that you filter by date or user to see the schedules?
------------------------------
Michael Tamoush
------------------------------
DanielJohnson2
4 years agoQrew Trainee
Hey Michael,
Thanks for the reply last week. I used the pipeline idea to add the parent record ID to the child record by matching the user it gets assigned to and the date it was assigned to the user and date on the schedule, and that's working.
What I'm trying to do now is stop users from creating more than one record on the scheduler table for the same day. In the past, a person who works 7 am to 9 am, and then 5 pm to 8 pm would enter two records on the scheduler table with the same date. I've added functionality in the form to cover for this, but I still want to try and stop users from adding more than one record per calendar day. Any idea how I would do that? I've already got the User + Date field, but how do I say in a data rule that a new record can't be created when one already exists with that value?
------------------------------
Daniel Johnson
------------------------------
Thanks for the reply last week. I used the pipeline idea to add the parent record ID to the child record by matching the user it gets assigned to and the date it was assigned to the user and date on the schedule, and that's working.
What I'm trying to do now is stop users from creating more than one record on the scheduler table for the same day. In the past, a person who works 7 am to 9 am, and then 5 pm to 8 pm would enter two records on the scheduler table with the same date. I've added functionality in the form to cover for this, but I still want to try and stop users from adding more than one record per calendar day. Any idea how I would do that? I've already got the User + Date field, but how do I say in a data rule that a new record can't be created when one already exists with that value?
------------------------------
Daniel Johnson
------------------------------