FieldOne Sky – Static Data Set-up


Here I will continue my posts about FieldOne Sky for Microsoft Dynamics CRM, this time I am going to look at some of the many pieces of static data that might need to be configured when you first implement FieldOne Sky.

The data maintenance options can mainly be accessed via the administration section of FieldOne sky;

In your FieldOne implementation planning it probably makes sense to list all of these static data items , review each one in turn and agree the required content. As once these are configured defining resources, services and incidents will become much easier.

Static data items to create include …..

  1. Skill types
  2. Territories
  3. Work order types
  4. Resource Categories
  5. Warehouses
  6. Priorities
  7. Work order sub status
  8. Pay types
  9. Site
  10. Service Task Types
  11. Time Off Reasons

NOTE: This post is still a work in progress! Other static items may exist. I will continue to add detail as I review the FieldOne documentation.

Skill types

Skill types are simply a text field describing the skill a resource needs to complete a particular service. A few examples are shown below.


Territories can be used to represent sales and service regions. These are optional. You can also associate each territory with a territory manager and list all the post codes (zip codes) that make-up that territory.

Note: From a UK point of view, the whole postcode needs to be entered. So “DY6 0HP” not just “DY6”. Depending on the size and complexity of your territories this may be an issue.

Initially in my set-up I have opted to simply say at a high level which accounts are in the West Midlands or East Midlands etc.

Work Order Types

Each work order will be given a work order type. In turn this can then be used to force the use of incidents and allocate a price list.

Initially I am setting my example system up without price lists, so I have left it blank. Although it is recommended that price lists are used.

Resource Categories

Resource categories are simply used to group resources. Each category can have a parent category to give a hierocracy of resources. See below how I have created “Equipment” and then defined “Maintenance Equipment” and “Gardening Equipment” as its children.


Warehouses are simply the name of a warehouse; these are used to show which warehouse a resource is associated with. Information that can then be used when managing inventory.


The priorities are used to reflect the importance of work orders, also each priority is given a colour to reflect the importance of a work order. The colour is then shown on the work order scheduling board.

Work Order Sub Status

The work order sub-status can optionally be used to give greater detail on the status of a work order. You can also define it the sub-status is the default when the work order first hits that system status.

For example:

When a work order is in the status “Open – Completed”, it needs to be reviewed by a manager and changed to “Closed – Posted” once the manager is happy all the required information has been entered. You might then want to have a sub-status of “Not Reviewed” and “Reviewed – Issues”, so that the manager can keep an eye out for work orders that need attention.

Pay Types

You may want to record what pay type a resource should be paid for a particular work order. Examples might be a standard rate and an overtime rate. For each rate you can define the % rate to be paid.

The percentage is relative to each resources hourly rate. So do they get 100% of the rate or more. Meaning overtime might typically be paid at 150%.


This option isn’t available directly in the admin menu! But is available when looking at resources or you could access via advanced find.

The site record is significant as each resource can start and finish their travelling from either their home address or their company address. Which is taken from site.

Service Task Types

The service task types are tasks you might want field agents to complete whilst delivering a service. So if you had a service maintain someone’s garden as task type might be to mow the lawn.

Each task s given a name but is also given an estimated duration which is used in the resource scheduling process.


Time Off Reasons

Time off reasons are simply a text field describing why a time off request has been made.


4 thoughts on “FieldOne Sky – Static Data Set-up

  1. Pingback: FieldOne Sky | Microsoft Dynamics CRM and Unified Service Desk

    • Hi Gagandeep

      Thanks for your comment.

      You are 100% correct, several of the entities have changed name since Field One Sky has been rebranded as Field Service. The posts I created previously all had a focus on the original Field One product. I do intend on creating a new set of posts talking more specifically about Field Service.


      • Hi Neil,

        True that. In fact as you mentioned, the Field One Sky solution itself has been re-branded to Field Services with many changes within.

        Will look forward to your post.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s