RMK - location object field

[former_member86739]

Hi All,

We are about to implement the RMK, and we are suffering with the Location object.

We will enable it to be able to use the multilocation advertisement function. However, we have 200+ locations, and even worse, sometimes we have 2-3 different companies in one location, so location values are duplicated, triplicated.

When recruiters choose advertising locations, they need to scroll down (filed is not searchable) and choose every single location they need, even though they want to advertise it in a whole country.

When internal candidates try to search for the location, they need to again scroll down and put a tick next to all locations they are interested in, so they can't just select their country.

Does anyone faces the same issue? Do you have any suggestions how to make this more user friendly?

Thank you!

[Angie_Pullano]

Hi Dorrottya,

It is not required to use the location object for job postings.

For example, while my current company has the location pull into job requisition fields for reporting/internal purposes (all position org data), the actual job posting location fields are a combination of picklists and free text fields.

Perhaps you could implement something similar?

Best regards,

Angie