Multi Client Selector Summary
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 ENTITY | ENTITY | Displayed Selector Summary | Displayed Client 1 Summary | Displayed Client 2 Summary | Displayed 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) |
| 1 | Property | 100/100 | 30/100 | 25/100 | 45/100 | 30/30 | 25/25 | 45/45 | |
| 2 | Property Name | 100/100 | 30/100 | 25/100 | 45/100 | 30/30 | 25/25 | 45/45 | |
| 3 | Property Status | 5/5 | 5/5 | 5/5 | 5/5 | 5/5 | 5/5 | 5/5 | |
| 4 | (hidden) Security Property Client | 3/3 | 1/3 | 1/3 | 1/3 | 1/1 | 1/1 | 1/1 | |
| 5 | Lease | 200/200 | 60/200 | 50/200 | 90/200 | 60/60 | 50/50 | 90/90 | |
| 6 | Lease Type | 2/2 | 2/2 | 2/2 | 2/2 | 2/2 | 2/2 | 2/2 | |
| 7 | (hidden) Security Lease Client | 3/3 | 1/3 | 1/3 | 1/3 | 1/1 | 1/1 | 1/1 | |
| 8 | Event | 1000/1000 | 300/1000 | 250/1000 | 450/1000 | 300/300 | 250/250 | 450/450 | |
| 9 | Event Status | 3/3 | 3/3 | 3/3 | 3/3 | 3/3 | 3/3 | 3/3 | |
| 10 | (hidden) Security Event Client | 3/3 | 1/3 | 1/3 | 1/3 | 1/1 | 1/1 | 1/1 | |
| 11 | Client | 3/3 | 1/1 | 1/1 | 1/1 | 1/1 | 1/1 | 1/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.
Comments
-
Thank you for sharing your insightful suggestion with us, Paul. Your time and effort are genuinely valued.
While we're not proceeding with your idea at the moment, this decision is based on our updated product enhancement and idea lifecycle processes, introduced in 2023 (details in our Idea Exchange FAQs).
Despite this, if you believe your idea still holds relevance, we invite you to resubmit it for review under the new guidelines. We're dedicated to offering the best user experience and prioritizing features and enhancements that significantly impact everyday usage of our software.
Your input is crucial to our community, and we sincerely appreciate your participation. Please keep those creative ideas and feedback coming – we always look forward to hearing from you.
Thank you again for your understanding and continued support.
PS: Please do have a look at the Idea Exchange FAQs to know more:
0
