Skip to main content

Access Practice Management – Resolve the ‘restricted picklist field’ job status error

Resolve the error “Status: bad value for restricted picklist field: Ready to Start” when creating jobs or uploading jobs via CSV in Access Practice Management. This error is caused by automation or validation rules enforcing a restricted job status value

Understand why the error occurs

This error occurs when:

  • A restricted picklist value (such as Ready to Start) is no longer valid

  • An automated flow attempts to set the job status to a value that has been removed or restricted

  • A job is created via CSV import or manually without meeting required conditions (such as start date rules)

The error message often references the Accountant Cloud Set Job Status on Create flow.

Resolve the issue by reviewing job status configuration

1. Check job status picklist values

  1. Review the Job Status picklist values

  2. Confirm whether Ready to Start is active and available

  3. Ensure the value is not restricted for the record type being used

If the value is inactive or restricted, the flow will fail.

Review or deactivate the job status flow

1. Locate the flow

  1. Open Setup

  2. Navigate to Flows

  3. Locate Accountant Cloud Set Job Status on Create

2. Modify or deactivate the flow

You can either:

  • Update the flow logic to use a valid job status, or

  • Deactivate the flow if it is no longer required

Deactivating the flow will stop it from blocking job creation.

Check job start date behaviour

1. Review start date rules

  1. Confirm whether the job start date is required

  2. Ensure the start date is today or earlier, if enforced by automation

  3. Avoid leaving the start date blank if validations are active

Invalid or missing dates can also trigger job creation errors.

Retry job creation or CSV upload

1. Test the fix

  1. Create a new job manually, or

  2. Retry the CSV upload

Confirm that the job saves successfully without the restricted picklist error.

When to raise a support case

If the error continues after reviewing picklists and flows:

  • Raise a support case

  • Include the full error message, flow name, and job status value

  • Note whether the issue occurs during manual creation or CSV upload

This helps determine whether additional configuration changes are required.

Did this answer your question?