FieldOne – Quick way to add Territories for the UK

Territories play are an important part in FieldOne and to understand the functionality provided by FieldOne you will need to setup territories.

Why do you need Territories

Once you have setup territories you can then use them with your resources at set their location.  The location information is used in

  • Work Orders
  • Scheduling assistant and routing engine
  • Filters on the Schedule board

Once you have Territories setup, you can add locations to your resources and work orders.  You can then schedule resources near to the work orders by searching or FieldOne can help you do this by automatically routing using the routing engine or the Scheduling assistant.


“In theory, theory and practice are the same. In practice, they are not.”
― Anonymous


I recommend CRM developers add theory to the practical knowledge, which is Why CRM Developers should always start with the CRM SDK.

To get full understanding of something you need theoretical knowledge and practical knowledge, this will allow you to find the limitations and functionality of something.

FieldOne is a great example of this because it’s not really until you start to actively use the system by setting up a demo environment or put in customers data until you really begin to understand how it works.  I call this active learning and it’s where the knowledge and practical experience come together to start creating a solution.

List of Territories

The territory on resources specify which area(s) the resource can be allocated work from.

The first step is you want to download some territories, I have found a list of cities

postcodes csv

You can see the postcodes have geocode details but in this case I’m not going to use them.


I now have a data to create some territories, I copy the postcodes csv to a new tab/csv, I deleted all the columns expect region and renamed this  Territory Name.  I selected Remove Duplicates so I had one row for each region, I save the file as Territory.csv


Territory postcodes

FieldOne can match partial postcodes, so if you add the postcode B32 it will match all B32 postcodes. To link postcodes to a territory you need to import into the entity called Zip Codes.  I used the original postcodes.csv and deleted all the fields except region and postcode and named the region Territory Name.  I saved the file as Territory Postcodes.csv

Territory postocde

Import the file using Import Wizard and select the entity Zip Code

Zip code import mapping

Next step

Zip code import

You will end up with 2700 territory postcodes

Next steps

You now have territories in CRM, the next logical step would be to create resources and then import a territory resource to the resource.

This sets up the territory where the resource can be scheduled for when using auto routing or the resource scheduler, if you do manual scheduling you can select any resource but you would probably filter by resource territory.

Below you can see I created some resources called

Birmingham Depot Truck Driver Test001 (to Test011) and created a service territory of Birmingham.  These trucks can be scheduled for Birmingham jobs

Birmingham Truck driver territory

It’s a quick way to get territories into FieldOne, it’s more likely individual clients will have set territories and the data above won’t be specific for your customers.

The steps above will help you get some default territories in FieldOne so you can start to see how territories and scheduling work.



FieldOne – Mobile app thoughts, problems and solutions

Varun Ravikumar

FieldOne is a service management solution built into the core CRM product, a key part of the FieldOne solution is the mobile app.  FieldOne Sky mobile app takes the CRM functionality out of the office to where the field agents are working, keeping the office and the field agent in sync.

See it in action here

Microsoft Dynamics CRM has made dramatic improvements in mobile functionality in it’s own mobile app to provide a rival excellent Resco mobile CRM App.  Resco functionality is slightly ahead of Microsoft CRM mobile application at the moment.

Built on Resco CRM Mobile App

The current mobile application is built using Resco mobile CRM app, this functionality is included when you buy an Enterprise license (things are always changing). The mobile app is a key part of FieldOne, Resco  didn’t want to give free access to the excellent Resco CRM mobile app.

To include FieldOne Sky mobile app, you are not allowed any non FieldOne functionality.

When I opened the mobile application I got an error saying

Customization contains an entity that is not allowed

The reason for this error is you had to pay for mobile access but now it is free with the caveat of no non FieldOne data or functionality available in the mobile app.

To get you FieldOne mobile application working you have to remove all sales entities from the woodford mobile solution, which can take a bit of trial and error to work out what to remove.  This great blog post by Neil Parkhurst lists all the entities not allowed

FieldOne Sky – Customization contains an entity that is not allowed

The other common error you might get is SA.NoUserData error,  another temporary error whilst FieldOne merges its code with the default CRM code.

I blogged the solution to this problem in the post

CRM 2016 – FieldOne – windows emulator SA.NoUserData error

How to test Mobile functionality

When I wanted to test the FieldOne mobile application I instinctively chose the Windows emulator.

The reason for is I haven’t got use to using Windows 8 and downloading apps on my laptop computer, in my mind apps live on phones and tablets.

Microsoft uses apps on Windows computers will be the same as on phones and tablets, which should encourage developers to create them.  The reality is if I’m on my laptop I don’t want to run an app, I want to run either the full program or browser based app and use the benefits of my laptop.

Apps run best on touch screen devices and offer a cut down version of an application on a laptop, it doesn’t make a great experience.   One of the reasons there are not many apps, the main reason is the target market of Windows devices is smaller than Apple and Android.

To test the FieldOne mobile application don’t use the emulator I believe it‘s not going to be updated and possibly removed and it might not be the same as the other mobile applications.

I have tested the mobile app on my personal android device, it works, I tested it on my Windows 8 laptop, full screen is annoying but it works well.

The future for FieldOne Mobile

FieldOne is integrated with the core Microsoft Dynamics CRM so it makes sense FieldOne will be developed in the default Microsoft Mobile application.

It will take time to match the functionality offered in the Resco FieldOne application but with time and will you can do achieve great things.

My first experience of Resco CRM mobile is it’s a great application and made mobile development is easier than I had imagined.

Here is an interesting interview with Ivan Stano, chief operating officer (COO) of, Inc

Microsoft Dynamics CRM Still Rich Ground for ISVs, Partners, Says Mobile Solutions Vendor

You can get a free 30 day trial for Resco and I recommend you try it, it’s good fun.

CRM with internet of things

Seeing FieldOne mobile in action, shows me Microsoft Dynamics CRM working with a mobile application.

When I have looked at the CRM mobile application before the functionality was limited and I didn’t see many convincing business cases for mobile applications working with CRM.

I believe mobile applications will become more common and along with Azure apps and Azure Service bus there will be increased integration with Microsoft Dynamics CRM.

The FieldOne service mobile sky application will give many people an introduction to the effective mobile applications working with CRM and give people something interesting to think about.

The out of the box CRM mobile application has improved functionality and offline capabilities, the tools are there and ready to go, don’t be surprised if you find yourself working on a CRM mobile application in the near future.

CRM 2016 – FieldOne – windows emulator SA.NoUserData error


FieldOne without mobile integration is like Hosk without CRM!

FieldOne without Mobile integration is like England without queuing


My first  FieldOne post, it will be the first of many as I will be using FieldOne a lot in 2016.

I have been getting to know FieldOne and going through the Learning Management System

FieldOne Learning Management System (LMS)

It’s a great resource with lots of material, the slight complaint I have is some of its out of date but FieldOne is going through changes whilst the product is incorporated into the main CRM product.


I wanted to try the mobile application, so I decided to try the Mobile Emulator.  I downloaded the mobile emulator, unzipped it.

I fired up the Mobile Emulator

Mobile Emulator

Go To Setup, fill in your details on the CRM tab

Setup mobile setup

I was getting an error

SA.NoUserData error


no permissions

Now What?

I am half way through my FieldOne training, I haven’t used the mobile app or emulator.  I couldn’t see any log files to help, so I was a bit stuck.

I searched the internet and even my blog didn’t come up with any solutions!! (this time)

I tried asking a question on the CRM Forum

FieldOne windows emulator SA.NoUserData error

The weakness of the forum’s is they are answered by CRM users but it means the more common your question the likely someone is to answer it.  In this case no one answered it.

FieldOne is relatively new so there are not many people who have knowledge about it, so for new products there won’t be many people who will have answers.

Neil Parkhurst to the rescue

If you are starting out with FieldOne, bookmark Neil’s blog, it’s an excellent resource for getting started with FieldOne.

In his blog he had a section on installing the FieldOne Mobile App

FieldOne Sky – Install Mobile App

In here he had a tip which resolved my problem

I had a problem that my application would not run on some mobile clients, giving an error of “SA.NoUserData” or conflict with meta data. To solve these issues;

2. In CRM, on the system user form add a field called “Allow Mobile Access (Depreciated)” and set this field to “Y”.


I went to the user form and added the field – Allow Mobile Access (Depreciated) to the CRM user form.

Add to user field

I opened my user and set the field to Yes.

Started the emulator again and pow, I started syncing

emulator synced

You would have to set all the users you want to have mobile access to Yes


The question is why is this causing an error.  I think the problem is caused because FieldOne is being integrated into the main CRM product there are lots of fields being depreciated and there might be a few bugs caused by this whilst the code catches up and new fields used.

I think Microsoft is allowing free access to the mobile client but I’m not sure and licensing questions are always confusing and changing.  That’s my guess of the problem.

This forum has the same solution as well.

FieldOne Mobile App – sa.nouserdata

As an extra tip, check you have the latest version of the CRM mobile app