- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
a month ago
I'm getting some odd behavior with the Granular Delegation widget and was wondering if anyone could point me in the right direction.
On the Add Delegates modal, I'm getting different lists between our two lower environments, and I was wondering if someone could point me to where the conditions are for the Delegate dropdown? I feel like I'm missing something obvious. The widgets have not been modified from OOTB.
Thanks in advance!
Solved! Go to Solution.
- Labels:
-
Employee Service Center
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
Hello everyone,
The cause of this issue was that the sys_user table needed to be reindexed.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
a month ago
If they really are OOB, they should show the same data (or at least, the same conditions should be applied).
First: check the data. Maybe one instance has less users active? Or they are configured differently (roles, or whatever). What exactly is the difference between a user record that is showing on one instance and not on the other?
Also check to see if the versions are the same:
- are both instances running on the same family version
- are both instances running on the same patch
- are all store apps up to date (and running on the same version)
My instance is sleeping (I wish I would get as much sleep as my instance) so I can't check where the widget is coming from, but it could be from the Employee Center app(s), or something like that. If that's updated and you are running on different versions, it could explain the difference you are seeing.
Please mark any helpful or correct solutions as such. That helps others find their solutions.
Mark
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
Hello everyone,
The cause of this issue was that the sys_user table needed to be reindexed.