It may seem like something easy to do but depending on the configuration of an environment it can be difficult to build a filter in Compensation Executive review that allows us to filter on several manager names (not ID) that are not connected through a reporting line, for the following reasons :

• The Executive Review doesn’t offer anything in standard to do this : we can only filter on one manager name or HR manager name at the time and then decide which levels below them in the reporting line we want to show.
• Username columns that show the name of a manager on the worksheet when mapped to EC Category = Job Info > Supervisor or EC Category = Job Info > HR manager job relationship are not yet supported in Executive Review and will not show in filter selection.
• We can try mapping a custom column of type “string” to EC Category = Employee Profile > Manager and another column to EC Category = Employee Profile > HR manager but we found after testing that it doesn’t return the name of the manager in all environments (sometimes it returns the ID and we are still trying to troubleshoot what is causing this). We recommend trying this solution (which is by far the easiest – when it’s working) and if it returns the ID of the manager and not the name then please follow guidance below.

Solution that always works

In this 20 minutes recording we show how to build a custom MDF object that allows planners and administrators to filter in Compensation Executive Review on several Line Managers or HR Managers (and by using their name vs userID) that are not in the same reporting line, which is not possible yet using standard tools.

The recording covers the following steps :

1. The creation of a custom MDF object (with externalCode=User so it can be used in Compensation) that will store the managers’ names.
2. The creation of a business rule that populates the managers’ names on save.
3. The creation of an integration center job that automatically captures changes on a daily basis thanks to a scheduled job.
4. How to link the MDF values to compensation template columns.
5. How to filter once the workaround is in place.

Conclusion

Not only does this solution always work but it also allows us to create deep job relationship filters, for example if we want to see on the worksheet who is a person’s “Level 3 manager” or “Level 4 manager” we can do so creating the appropriate new field in the custom MDF object and then by nesting the mapping in the On Save business rule of the MDF object (Example for level 3 : Job Info > Supervisor > Job Info > Supervisor > Job Info > Supervisor.name).