website logo
Navigate through spaces
ChartHop documentation
⌘K
ChartHop Help Center
Getting around in ChartHop
ChartHop Video Library
Navigating ChartHop
Home page
Org Chart
Map
Data Sheet
Employee Profiles
Implementing ChartHop
ChartHop implementation overview
Creating your ChartHop org
Configuring your Org settings
Inviting users and setting permissions
Permissions and security
Creating and managing groups
Integrations and bundles
ChartHop for Administrators
Planning
Managing employee data
Creating reports and analytics
Managing people and jobs
Performance reviews
Building custom forms, tabs, and documents
ChartHop for Developers
ChartHop connect
Developer basics
Events
Syncing data to/from ChartHop
Partners
Sequoia getting started
Resources
Available ChartHop packages
ChartHop Standard Terms and Conditions
ChartHop Basic Agreement
Data Processing Addendum
Privacy policy
Security statement
Subprocessors
FAQ
Docs powered by archbee 
website logo

Troubleshooting job matching fields

This section covers a series of potential issues you may run into when setting up or using fields in ChartHop to match payroll app requisition code, as well as their recommended solutions.

Creating ChartHop fields to match requisition codes

Does my job matching code have to use a custom field?

No, you can use a custom or built-in fields as long as the field type is a short text. We recommend using a custom field so that you can customize the name of your job matching field.

Can I have multiple open jobs with the same job matching code?

Yes. If you have multiple open jobs with the same job matching code, ChartHop will match the job with the req code set on it the earliest (note this may be different from which job was *created *earliest).

Does my custom field have a specific name like “req code”?

No. No, you can use any phrase to name your job matching code.

Using ChartHop fields to match requisition codes

Why can’t I find the job matching code value on a person?

The requirements for the job matching code are that the field belongs to a job. When you set up the mapper from the remote system → [job matching code field], ChartHop works behind-the-scenes and uses the job matching code to find an open job for a new hire, then discards the value.

If you want to see the job matching code value saved on a person, you can create a separate field and mapper to track that.

Do I need to delete the job matching code value from the person on the HRIS once the matching is complete?

No. The job matching code is only used on new hires and won’t impact any employees who are already in ChartHop.

Note that changing the value in the HRIS will still update the value on the underlying job in ChartHop.

Why didn’t a(n) (existing) person transfer jobs when I changed their requisition code?

Code matching only applies to new hires and open jobs, not existing employees or internal transfers.

Updated 18 Jan 2023
Did this page help you?
Yes
No
UP NEXT
Building forms
Docs powered by archbee