Best Of

interested typ - do you copy the symbols or are you able to use the keyboard to enter the uni code?  I have tried with the keyboard to insert an up arrow - [Alt] + 2191 - but get a capital A with a small circle on top [Å].  However, I will now be using unicode characters as presented by you and Bettina Clausen so thank you both for the idea - really great solution.

Bob Gill , did the solution using ATOs from interested typ work for you? To control the members that users see, you can use a SELECT cube and 'hide' those members not wanted. I've just created a video on it called 'Sort and Select'. It should be released either today or tomorrow but in essence:

1.  Create a single entity cube, 

2.  Create a dataview and add the cube 

3.  Select data entry on

4.  Change output to check boxes

5.  Add and hide cube to target object

6.  Place cube in Filter a of target object and make > 0.5

7.  Select the cheekbones of members to show 

8.  Save data entry

9.  Target object will only show checked members. 

Hi Etienne CAUSSE Firstly, like Davide Genini, I do not think I understand fully Hervé BEURET requirements. The reference to a multiple database model was to respond to a percieved requirement to prevent the user from circumventing security and seeing what they should not. Secondly, I did not read the complete exchange between Hervé BEURET, Davide and yourself as I was responding on the train using my phone. - Sorry for adding to any confusion.

My first point hasn't changed.  My response is based on an assumption that Hervé BEURET needs to restrict access to entity members for specific users. If this was the intention, then a single db and capsule can be used but the control must also be incorporated throughout the database architecture.

I develop models for external clients that share a database. The security is handled in the way you have already described but also with a matrix mapping cube. Db security is set as follows where a client user group are restricted to seeing data on for client number 1:

Sample entity: PROPERTY > PORTFOLIO

Code + Desc

1 - Client 1a

2 - Client 1b

3 - Client 2a

4 - Client 2b

5 - Client 2c

@user
SELECT CLIENT = 1
SELECT [SECURITY_CLIENT_PROPERTY]=1
SELECT [SECURITY_CLIENT_LEASE]=1
SELECT [SECURITY_CLIENT_EVENT]=1

NOTE:

1. Entities CLIENT and each of the mapped entities are all duplicates and share the same mapping using the mapping cube.

2. Each tree datareader (Property, Lease and Event) contains the relevant SECURITY entity.

3. Each Cube datareader contains only the entity CLIENT - which has been mapped to the SECURITY entities and a single matrix cube.

With the above configuration, I am able to control what members of shared/common entities each, disparate client, can see. I also secure the cube values that they have access to.

users with this config would see only:

 - PORTFOLIO entity members for the first 2 members (1 & 2)

- Cubes would only show values / entries mapped to the PROPERTY / LEASE / EVENT for client 1

- GVA Analysts will see all entries and can simply select CLIENT 1 to see exactly what the external client sees

The use of the mapping cube means that GVA analysts can have unrestricted access to the database and select the CLIENT or CLIENTS they wish to view.  Using a procedure to select the SECURITY ENTITYs based on the Mapping cube, internal analysts can work in controlled and secure stable data structures relating only to what they need.

Now, it is probable that I have completely missed the point and if this is the case I'm really sorry. However, in the event that I assumed correctly, then I have at least suggested that it is possible to control access to entity members without using the local dataview/object configurations.

It is my intention to demonstrate this structure at some point, once I have the time to create the test model, video and screen shots.

Hi Adam Elvin.  Accepting that there are many things that will result in errors such as the invocation one, the commonest reasons that I've encountered errors of this nature has been as follows:

1.  Entity or Cube removed but reference remains in datareader resulting in error on running reader.  Usually spotted through error on re-running dataload process and having a message in bottom right of screen - hard to see on a 27" UHD monitor. 

2.  Screen left open when database work was carried which deleted/altered an entity or cube used in a dataview/chart object.  This also resulted in a corrupt capsule in which it was impossible to delete said screen.  I had to re-name the screen 'DO NOT USE' and rebuild the screen.  The capsule is still carrying this corrupted screen.

I'm not claiming that the 2 points above are what has happened to you, just that you might want to consider what changes you've done and maybe check for messages.