Tables view: Ability to share specific tabs with the collaborators rather than all tabs

  • PageantAds
    Asked on October 29, 2020 at 9:23 AM
    Thank you... please add to that request, I would like to be able to duplicate the submitted data within the 'tables' view, create and lock the filter, and share ONLY that tab with a viewer. I would like that viewer to be able to provide feedback within the view either accepting or rejecting a specific record in the table.
  • Patrick_R
    Replied on October 29, 2020 at 9:28 AM

    Hello! Please find answers to your concerns below.

    - I would like to be able to duplicate the submitted data within the 'tables' view

    Kindly note that this is already possible. Following is how you an duplicate a tab within the table view. But please note that this type of duplication only the current submissions data from the main table. So, the submissions that you receive after duplicating will show up in the main tab but not in the duplicate tab.

    1603978042 5f9ac33a7c012 Clone of Lowe's Screenshot 10

    Let us know if this doesn't fulfil your purpose.

    - create and lock the filter

    This has already been forwarded as a feature request.

    - and share ONLY that tab with a viewer

    I've added a new feature request for your requirement here.

    - I would like that viewer to be able to provide feedback within the view either accepting or rejecting a specific record in the table.

    Currently, there are two types of roles available, i.e. 'view', 'view & edit'. In 'view & edit' role, collaborator can edit all cell entries, it is not specific to just one cell.

    Q1) Can you please elaborate this point?

    Q2) what kind of feedback are you looking to collect and what exactly do you mean by accepting or rejecting?

    Kindly provide us an example, so that we could better understand your requirement.

    Awaiting your response.

    Thank you!

  • PageantAds
    Replied on October 29, 2020 at 9:41 AM

    Q1) As an application:

    1. We have a jotform that we use to collect information about models. A model completes the form, providing requested information that includes their body stats: height, size, etc.
    2. We have clothing designers who complete information in another database. They provide us details about the models they need to wear their designs on our runways. These include the same body stats: height, size etc.
    3. We have a field in the model database that lists the designers from each show.
    4. We select the model for each designer and assign them thru this field.
    5. We can sort for all models within a specific show for a specific designer and create a new tab for that sort.
    6. We show that tab in card view so that the designer has a 'model card' for each of his looks.
    7. WE DO NOT want the viewer to be able to change the filter and see models assigned to a different designer... only their's.
    8. We would then like to have the designer select from another field, either Yes or No.. (accepted/not accepted) and to be able to add a reason for not accepted if that is chosen.
    9. It is imperative that they be unable to edit the model's stats or anything related to the model. Those fields have to be read only.

    I hope this helps clarify what we need for future development. You are doing a great job and we appreciate it.

  • Richie JotForm Support
    Replied on October 29, 2020 at 10:27 AM

    Thank you for the added information.

    My colleague has forwarded a feature request already and once we have further information, you will be notified at this support ticket.

  • PageantAds
    Replied on October 29, 2020 at 10:28 AM

    Thank you. I did submit multiples but not to create confusion. :) Thanks.