Multi Client Selector Summary

Idea created by Paul Wyatt - GVA on Mar 16, 2018
    Open for voting
    Score2
    • Paul Wyatt - GVA
    • rubicon

    THE IDEA

    I would like to suggest adding a feature which would allow a selector object to display only the total number of entity members available to a user when that user has been restricted in what they can see. 

     

    WHY

    The present selector object displays the total number of members that exist within an entity.  I have a multi client data model which is accessed by various external clients. The database has three trees and the security entity Client.  Using my current setup and a database custom script, clients are prevented from seeing both the entity and cube values of other client data but not the total number of members of an entity.  This presents an issue when a client wants to know the total number of members available to them over how many they have currently selected. 

     

    Below is a table to illustrate what is seen and what a client should see when using a selector in summary view. 

    • Column (h) is the usual display of a selector summary where no security ha been allied.
    • Columns (e-g) are what each client sees with security applied to their access profiles.
    • Columns (i-k) is what a client with restricted access should see in a selector summary.

     

    BASE ENTITYENTITYDisplayed Selector SummaryDisplayed Client 1 SummaryDisplayed Client 2 SummaryDisplayed Client 3 Summary

    Desired Client 1 summary

    Desired Client 2

    Summary

    Desired Client 3 Summary
    (a)(c)(b)(h)(e)(f)(g)(i')(j)(k)
    1Property100/10030/10025/10045/10030/3025/2545/45
    2Property Name100/10030/10025/10045/10030/3025/2545/45
    3Property Status5/55/55/55/55/55/55/5
    4

    (hidden)

    Security Property Client

    3/31/31/31/31/11/11/1
    5Lease200/20060/20050/20090/20060/6050/5090/90
    6Lease Type2/22/22/22/22/22/22/2
    7

    (hidden)

    Security Lease Client

    3/31/31/31/31/11/11/1
    8Event1000/1000300/1000250/1000450/1000300/300250/250450/450
    9Event Status3/33/33/33/33/33/33/3
    10

    (hidden)

    Security Event Client

    3/31/31/31/31/11/11/1
    11Client3/31/11/11/11/11/11/1

     

    ALTERNATIVE SOLUTION

    One way to currently address this issue is to first store the total value of members {Y} of each entity divided by client and then create a custom object for each selector required.  A layout can be used to present the 2 values {x/y} for 2 cubes and a capsule procedure must then be created for each selector and associated with the custom object.  I have carried out this work and found the it to be laborious and prone to mistakes due to the repetition of steps to create 13 custom selectors.