Is there a way to dynamically set a list view? - Forum - Rollbase - Progress Community

Is there a way to dynamically set a list view?

 Forum

Is there a way to dynamically set a list view?

This question has suggested answer(s)

I have a generic tab that I would like to display a specific view based on the user that is currently logged in.

Initially I was planning on just having a section for each of the 6 possibilities and then set the visibility of that section based on the logged in user, but I am not able to add the same view component to each of the sections (seems odd).  

Any suggestions?

All Replies
  • Hi Jason,

    You can have one section with the object view and just create a list view per user. To do that:

    1. In the new/edit page of list view go to the bottom part (Permission section)

    2. Uncheck all view permissions for roles to avoid view conflict with your users.

    3. Go to the "Individual Users" and select the user you want to have access view to this.

    4. Make sure to check the "View" checkbox since it was not automatically checked.

    5. Do the same procedure to other user's view.

    Hope this may help.

    Thanks,

    Orchid

  • That doesn't quite solve my issue.  The users have access to a number of different views for this object and when they are looking at the Object tab they will need to select the view they need.  However I am trying to build a "Dashboard" type tab for them that has information that their team is working on.  So my thought was to create a view that displays the dashboard information along with various other KPIs and then show or hide that section of the page based on the Team that is assigned to their user.  

    At this point I have more or less recreated my views as HTML reports and am displaying the correct report based on the user.  It's a little more work, and not quite as much functionality but I think it will do.

  • You can use client-side API to show/hide page's sections and tabs. Please see Chapter 7 for more info.

  • Hi Jason,

    Another way to do this is to create multiple tabs with list views specific to users.

    Same as the procedure above, set the permission of each tabs.

    1. In the Tab properties

    2. Uncheck all view permissions for roles to avoid view conflict with your users.

    3. Go to the "Individual Users" and select the user you want to have access view to this tab.

    4. Make sure to check the "View" checkbox since it was not automatically checked.

    5. Do the same procedure to other user's view.

    Hope this will help.

    Orchid

  • Hi Jason,

    Is the suggestion above works for you? or do you still have any questions?

    Thanks,

    Orchid

  • Hi jbolstad,

    Page Versions is what you are looking for. You can have multiple versions of the list page (each set to show a different view of the same object list) and then according to your specific user assign page versions that  particular user would see.

    Please check the documentation link shared below for further info. Do get back if you have any doubts.

    documentation.progress.com/.../index.html

    Regards,

    Santosh


  • On 03 Jul 2014, at 16:15, Orchid Corpin <bounce-ocorpin@community.progress.com> wrote:

    Reply by Orchid Corpin

    Hi Jason,

    Another way to do this is to create multiple tabs with list views specific to users.

    Same as the procedure above, set the permission of each tabs.

    1. In the Tab properties

    2. Uncheck all view permissions for roles to avoid view conflict with your users.

    3. Go to the "Individual Users" and select the user you want to have access view to this tab.

    4. Make sure to check the "View" checkbox since it was not automatically checked.

    5. Do the same procedure to other user's view.

    Hope this will help.

    Orchid

    Stop receiving emails on this subject.

    Flag this post as spam/abuse.


  • Please refer to this documentation link documentation.progress.com/.../index.html

    Thanks

    Srinivas

  • I need to set the List View dynamically based on a "record type" (picklist) to handle a polymorphic dependency. Depending on the "type of record" being viewed, a could like the view of child records to be different (same object with different columns showing). This is not based on user profiles but on the type of record.