List Calculation configuration not taking effect to other users?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-07-2017 09:25 PM
Hello folks,
Has any one ever experienced List Calculation that has been configured which works as expected to yourself, but others?
In a related List (say Resource Plans) -> The List Calculation is configured on Allocated Cost field (see below screenshot)
Once created, you can see the total of cost of $1,409.10, but this does not take effect to other users with the same parent record and exactly the same related list. (see below screenshot)
Since the user doesn't have the role to configure list, the configuration is not applicable.
I've tried Related Lists under System UI, it doesn't seem to configure the List Calculation.
I was wondering if it could be configured globally.
Any help would be appreciated.
Thanks,
- Labels:
-
Scoped App Development
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-07-2017 11:58 PM
For the user you're using to verify if the change took effect... have you made sure their list view isn't already personalized?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-08-2017 02:59 PM
Thanks Robert. I checked the Personalized List Columns settings on the impersonated user,
If I disable all settings, see screenshot below
the summation is still now showing
as for myself, disrespectful of the settings, the summary appears to display always
Thanks,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-08-2017 05:49 PM
Hello Robert again,
I think I found the way to make it global. That is to configure the Sum field to true on the allocated_hours and allocated_cost via System UI -> List -> Table=resource_plan, instead of directly configure the List Calculation in the related list of resource plan under parent demand.
Ensure the User field is empty which means this applies by default.
it has seemed to work after impersonating a different user.
Thanks again for your advice.