All Collections
CLIPxe
Global Replacements
[CLIPxe/QCLIPxe] Global Replacement: Change Job Type From Automatic to Zone
[CLIPxe/QCLIPxe] Global Replacement: Change Job Type From Automatic to Zone

How to change the Job type for all jobs globally (all at the same time)

Jonathan Conaway avatar
Written by Jonathan Conaway
Updated over a week ago

Global Replacement: Change Job Type From Automatic to Zone

This global replacement will allow you to change a Job's schedule type from automatic scheduling over to zone scheduling for your snow jobs. In this example, we will be using a job called "Landscaping Maintenance." You can perform this replacement on any job in your database. To begin, click "Pattern Jobs" button on the main screen.

From the screenshot above, we will look for the number of the job that we want to make the change over to zone scheduling. In our example, this will be "Job Number 2 Landscaping Maintenance." Click "Return." Now lets go to Files> Global Replacement> Replace Information.

Make sure that Job is selected under Choose Database then click Choose Field.

Scroll down to the bottom of the field list to find JB.Schedule Type-Zone/Auto field, then double click. Now the field will be put under the Fields Chosen box. Click Replace With.

The window will ask if you are changing the schedule type from zone or auto. For this example, we will type "Z" for Zone Jobs. Now click Ok. Click Choose Condition.

For the condition, we will want to choose "Job Number 2" for the landscaping maintenance job. This will replace schedule types for job number 2. For Step 1 - choose "Field From List", double click or press enter on JB (Job Number).

For Step 2 - Choose Operator, click Equals then press Enter.

For Step 3 - Enter comparison value. Type 2 in the field, then press enter.

The end result should show JOB-JOBNUM = 2. Click "Use This Condition."

The Replacement Command should show that we are replacing all Job Number 2 to Zone Scheduling. Click Perform Replacement.

Let us know if you need further assistance!

Did this answer your question?