Hi Team,
I have a healthcare client that wants to leverage the Jobs vertical.
I noticed that the address field, by default, is greyed out - so what I’ve done is create a custom field for this entity type’s address.
My client wants to use the jobs vertical with the locator functionality, so it is a shame that I cannot leverage the builtin address field. What is the reasoning for it not being enabled on job entities?
Best,
Luc
Hi Luc,
Totally agree - using the locator functionality with the jobs vertical is useful! For the built-in jobs entity type, you can use the built-in Location field. This allows you to choose between:
An existing location in the Knowledge Graph - This links the entity and will pull in the address of that linked location.
An external location in the form of City, State
You can then make the address fields searchable by making builtin.location an nlpFilter. Hope that helps!
Hi Kristy,
I should have clarified that for this client they advertise jobs that aren’t necessarily at one of their locations - they are often remote service jobs.
Can I simply add an arbitrary external location to each job entity? I took a look when trying to add the field to the job entity type but could not find it. 
Thank you for your response BTW. That is very helpful.
The Location field is built in for the Job entity type and should fall under Core Information when you go to edit your jobs entities. We recommend using External Location (City, State) for remote service jobs that are not tied to a specific address.
