Forum Discussion
LauraThacker
6 years agoQrew Captain
These solutions to cover various options and you will need a combination of them depending on how you are setting up access to your tables for the roles. These methods would be necessary if the Reply user was not going to be the same person, necessarily.
1. Build a summary field between Feedback < Replies to count the # of Reply records. Then update your [Add a Reply] formula to hide when the [# of Replies] >=1 (essential)
2. Hide your Replies table from the Users so they can only access the Replies through a Feedback record. (optional if you deploy 6 or 9)
3. Turn on (off) the [Hide Add Button/Links] at the Role Level to the Replies table so the Users cannot try to add Replies via the + sign on the purple bar (optional if you deploy 6 or 9)
4. Build a record picker that only lists Feedback with no replies so that if a user does try to add a record to the Replies table; they cannot select the Feedback record because it will not be listed (optional)
5. Turn off the ability to Grid Edit the Replies table; so they cannot try to create records via grid edit
6. Write an automation to delete any replies which are created when saved and the [# of replies] >= 2
7. Turn off the Users ability to edit Replies
8. Prevent users from copying-replies to create additional ones by turning off the view icon in the embedded report
9. Summarize the MIN record ID# of the Replies to a Feedback; then add a lookup field of the MIN Record ID# to the Replies. Use a checkbox to identify Replies which are not "original" replies; and use a scheduled-automation to delete records where the [Checkbox] field is true.
1. Build a summary field between Feedback < Replies to count the # of Reply records. Then update your [Add a Reply] formula to hide when the [# of Replies] >=1 (essential)
2. Hide your Replies table from the Users so they can only access the Replies through a Feedback record. (optional if you deploy 6 or 9)
3. Turn on (off) the [Hide Add Button/Links] at the Role Level to the Replies table so the Users cannot try to add Replies via the + sign on the purple bar (optional if you deploy 6 or 9)
4. Build a record picker that only lists Feedback with no replies so that if a user does try to add a record to the Replies table; they cannot select the Feedback record because it will not be listed (optional)
5. Turn off the ability to Grid Edit the Replies table; so they cannot try to create records via grid edit
6. Write an automation to delete any replies which are created when saved and the [# of replies] >= 2
7. Turn off the Users ability to edit Replies
8. Prevent users from copying-replies to create additional ones by turning off the view icon in the embedded report
9. Summarize the MIN record ID# of the Replies to a Feedback; then add a lookup field of the MIN Record ID# to the Replies. Use a checkbox to identify Replies which are not "original" replies; and use a scheduled-automation to delete records where the [Checkbox] field is true.