Page 1 of 1

Publishing and isPublic field - 02314706

Posted: Mon Aug 22, 2016 5:36 pm
by philipjfulcher
I've been working with a client for a couple of years on their website which includes Bullhorn integration. We use the WebServices API to pull a daily query of published jobs and build pages on the site based on the jobs returned. To mark a job to be published on the site, we've had the client use the "Publish" menu on the job to publish to the corporate job board. When they're ready for it to come off the site, they remove it from the job board. In the backend, we've queried using "isPublic = 1" to search for these jobs. This worked fine for awhile.

Recently, we've noticed this isPublic field is not changing the way we'd expect it to. Previously, the isPublic field would no longer be 1 if the job were unpublished. But now I'm looking at a job listing in Bullhorn that says unpublished in all job boards, but still has isPublic = 1.

Any idea what's going on here? this worked previously, so I'm not sure what might have changed. Are we not using the field correctly? Has the behavior of that field changed?

Re: Publishing and isPublic field - 02314706

Posted: Wed Aug 24, 2016 10:26 am
by pmularski
Good morning Philipjfulcher,

This can happen when a job is copied. A copied job will pull the isPublic = 1 setting even if it is not technically published to any website. That is the most likely cause in a case such as this one.

Re: Publishing and isPublic field - 02314706

Posted: Wed Aug 24, 2016 10:36 am
by philipjfulcher
Is there any way to get one of these copied posts back to an isPublic value of 0?

Re: Publishing and isPublic field - 02314706

Posted: Wed Aug 24, 2016 10:47 am
by pmularski
Good morning Philipjfulcher,

You can either run an API update, or manually change the field in Bullhorn. Your client would need to make the field available first, but it is a viable option.

Re: Publishing and isPublic field - 02314706

Posted: Thu Sep 08, 2016 5:11 pm
by philipjfulcher
Is there any other solution for this? My client is uncomfortable exposing that field for editing. They want control over who within their organization can post to job boards, and using the publishing interface was the easiest way to do this. Why isn't the isPublic field updating as we publish or unpublish using the publishing interface?