Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hello All,
I am trying to implement a section access logic, also looking for a solution which should not impact the opening time of the application much.
Below is the scenario:
| Country | Category | Sales |
| A | Data1 | 100 |
| B | Data1 | 21 |
| C | Data1 | 23 |
| D | Data1 | 12 |
| A | Data2 | 34 |
| B | Data2 | 21 |
| C | Data2 | 45 |
| D | Data2 | 21 |
So, suppose when a user "Jyothish" logs in, he should have access to see Sales data for Country "A" and where category is "data 1" , but he should have access to see sales of all countries where Category is "Data2".
So output data should be like this, i mean the data he should be able to see:
| Country | Category | Sales |
| A | Data1 | 100 |
| A | Data2 | 34 |
| B | Data2 | 21 |
| C | Data2 | 45 |
| D | Data2 | 21 |
Thanks in advance.
Regards
KC
Hi,
When i have done it in the past it has not been to bad for effecting the opening times. I would normally set it up as an access group, so i can try to minimize the amounts of combinations attached to the users.
Like below.
| Access | NTNAME | AccessLevel |
|---|---|---|
| User | DOMAIN\USERNAME | IT |
Then set up the groups.
| AccessLevel | AccessKey |
|---|---|
| IT | AData1 |
| IT | BData1 |
Mark
What impact on opening times are you talking about? Seconds? Minutes?
Data reduction always impacts the opening time, especially when having a complex data model with many rows. But it should be about the same as making selections in your document.
Best,
Peter