versago3:user_setup
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
versago3:user_setup [2022/08/02 16:07] dlee [Use the User Account Filter in a Data View] |
versago3:user_setup [2023/11/30 11:27] (current) dlee [Roles] |
||
|---|---|---|---|
| Line 37: | Line 37: | ||
| </ | </ | ||
| + | <WRAP center round important 80% > | ||
| + | Users should set their timezone under the User Profile page in order to properly display Calendar data views. | ||
| + | </ | ||
| ======Roles====== | ======Roles====== | ||
| Line 48: | Line 51: | ||
| - Click the [**Add Role**] button to create a new user. | - Click the [**Add Role**] button to create a new user. | ||
| - Click a row in the listing to edit the role. | - Click a row in the listing to edit the role. | ||
| + | |||
| + | |||
| + | <WRAP center round info 80%> | ||
| + | Click to the right of the Select All box to sort by selected users | ||
| + | {{ : | ||
| + | </ | ||
| + | |||
| Line 79: | Line 89: | ||
| ======Implementing User Account Filters====== | ======Implementing User Account Filters====== | ||
| + | |||
| + | {{ : | ||
| To illustrate how a user account filter works we will use the salesperson example. We will be using the SAP Business One data structures. | To illustrate how a user account filter works we will use the salesperson example. We will be using the SAP Business One data structures. | ||
| Line 105: | Line 117: | ||
| The data view should include in its result set a field with the same name as that of the UAF. In this case, SplCode | The data view should include in its result set a field with the same name as that of the UAF. In this case, SplCode | ||
| - | |||
| Using our example, if the user described above runs the data view, they will only see records where the “SlpCode” value equals 1. | Using our example, if the user described above runs the data view, they will only see records where the “SlpCode” value equals 1. | ||
| **Note:** Both User Account and User Applied filters can be used in the data view at the same time. | **Note:** Both User Account and User Applied filters can be used in the data view at the same time. | ||
| - | ===== Multiple Profile Values ===== | ||
| - | |||
| - | In the examples above, the value “SlpCode” has been present in the data being reported (the sales document). So, the profile filtering works with no issues. However, there may be situations where the name of the filtering column does not match This value in the source table. This situation can be addressed using multiple values in the profile setup. | ||
| - | |||
| - | In this example, we have some documents where the column to be filtered is named “SlpCode” and others where the column to be filtered is named “SlpCodeX.” As shown in the image below, we have created two profile entries. | ||
| - | |||
| - | {{ : | ||
| - | |||
| - | One shows that the filtering column name might be “SlpCode” and the second shows that the filtering column name might be “SlpCodeX.” Now, we can use the same profile and the filtering will occur if a column name “SlpCode” or “SlpCodeX” is found. | ||
| ---- | ---- | ||
versago3/user_setup.1659470824.txt.gz · Last modified: 2022/08/02 16:07 by dlee
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial 4.0 International
