Menu Close

Blog

Slide 1

Microsoft Business Applications Blogposts, YouTube Videos and Podcasts

Helping Businesses with Technology

Slide 2

Microsoft Business Applications Blogposts, YouTube Videos and Podcasts

Helping Businesses with Technology

Slide 3

Microsoft Business Applications Blogposts, YouTube Videos and Podcasts

Helping Businesses with Technology

previous arrow
next arrow

What are Agreements in Microsoft Dynamics 365 Field Service

Hi Everyone,

Today i am going to discuss about the Agreements in Field Service.

So lets get started.

What is Agreement in Field Service:
An Agreement is a contract with the customer, what needs to be performed under what contract.

1) Agreement is a Framework for automatically generating Work Orders and Invoices.
2) Can have a recurring schedule for a period of time
 – Example: Monthly inspection for two years

3) Can be used to define multiple schedules in a single agreement

4) Ideal for items like preventative maintenance

For example : there is a requirement to landscaping the garden.

So for that there should be an Agreement.

A single Agreement can have multiple booking setups defined.

– Once a week schedule someone to go out and provide lawn care.

-Every two weeks scheduling someone to go out and provide weekly landscaping such as hedge        pruning.

– Once a month clean windows and exterior services.

Finally Invoice once a month that invoices for all service provided.

Below is the Agreement record image:

An Agreement record should have following field values in order to agree a contract with a customer.
Service Account and Billing Account
Start & End Date of Agreement
Duration of Agreement
System Status & Sub Status
Price List: what is the price for the agreement.
Service Territory: what is the territory.
Taxable

There are Booking setups and Invoice setups on the Agreement record where you can define what are the bookings and Invoice setups can be scheduled to where the work orders and bookings created in the system.

Let me show how to create an Agreement on the Field Service.
Go to Dynamics 365 > Field Service > Agreements

I hope this helps.
For Microsoft Dynamics 365 Consultancy/Training/Support/Licensing
Contact us: https://www.gmritsolutions.co.uk
Email: admin@gmritsolutions.co.uk

Share this:

Points to remember Fields in Microsoft Dynamics 365 Field Service – Work Order Creation.

Hi Everyone,

Today i am going to share few points, these points needs to be remembered.

Let’s get’s started.

In the Microsoft Dynamics 365 Field Service, when you create new Work Order the following fields needs some attention and needs to be taken into account.

Work Order Type: Type of Work Order (Inspection, Break Fix, Install etc.)

Price List: Price List attached to the Work Order

Priority: Priority Level(Low, Normal, High)

Work Location: Location where the work will be taking place.]

Related to: Other records related to this Work Oder
 . Parent Work Order
 . Agreement
 . Opportunity
 . Case

Preference: Specific time and date preferences for this work order.

I hope this helps.
For Microsoft Dynamics 365 Consultancy/Training/Support/Licensing
Contact us: https://www.gmritsolutions.co.uk
Email: admin@gmritsolutions.co.uk

Share this:

Microsoft Dynamics 365 Field Service Work Order Relationships

Hi Everyone,

Today i am going share some information about the “Work Order” Relationships.

Let’s get’s started.

Work Order Types– Categorize Work Orders(Installs, Repairs, Preventative Maintenance)

Priority – Rates the importance of the Work Order. Can be configured and increased or decreased as needed; reflected on Schedule Board.

Service Territory – Organize Work Orders and resources by geographical area.

Incident – Common issues that a customer could report

Product – Items that may be needed for the issue

Service – Determines the services required to complete the Work Order.

Service Tasks – Check list or step by step instructions

Characteristics: Skills, Knowledge or certification required.

I hope this helps.
For Microsoft Dynamics 365 Consultancy/Training/Support/Licensing
Contact us: https://www.gmritsolutions.co.uk
Email: admin@gmritsolutions.co.uk

Share this:

Microsoft Dynamics 365 Field Service Work Order Life Cycle

Hi Everyone,

Today I am going to discuss about the Field Service Work Order Life Cycle Process

Let’s get’s started.

Work Order Life Cycle:

1) Work Order Creation:

What happens: New Work Order created, Assigned incidents, products, services, etc.

Who Performs: Agreement: Auto generating or recurring

Case:Work Order can be created from Case entity.
Opportunity: Work Order can be created from Opportunity entity.
Manual:

Work Order can be generated from sales or service or manually.

Work Order Status: Open- unscheduled
Booking Status : N/A

2)Schedule:
What Happens:
Bookable resource booking created.
Resource assigned.
Date and time specified.

Who Performs:
Dispatcher(Manually).
Field Agent(manually or mobile).
Dispatcher with help of scheduling assistant.

Work Order Status: Open – Scheduled
Booking Status: Scheduled.

3)Dispatch:
What happens:
Field Agent notified of Work Order.
Who Performs: Notification sent by system to Field Agent, customer or others

Work Order Status: Open – scheduled
Booking Status: Scheduled(Custom Status)

4)Service:
What Happens:
Work Order carried out
Who Performs: Field Agent
Work Order Status: Open- In Progress > Open- Completed
Booking Status: Travelling, In Progress Completed.

5)Review/Approval:
What Happens:
Work done and information is accurate.
Who Performs: Supervisor/Manager.
Back office accounting.

Work Order Status : Open – Completed > Closed -Posted
Booking Status : Completed

I hope this helps.
For Microsoft Dynamics 365 Consultancy/Training/Support/Licensing
Contact us: https://www.gmritsolutions.co.uk
Email: admin@gmritsolutions.co.uk

Share this:

Microsoft Dynamics 365 Field Service Resco MobileCRM project publish points to remember

Hi Everyone

Today i am going to share few points which needs to be considered when publishing the Resco MobileCRM Project.

Open the Project you want to publish.

Be you are publishing to the correct version
  > In the Field Service Mobile Application, click about
  > Publishing to a higher version will break the mobile app.
  > You can publish multiple projects as needed.

Please note: If you are not seeing your changes in the mobile application, verify that a security role you are a member of had the appropriate permissions.

When you are publishing the changes make sure you select the correct the version otherwise you will the solution, but it can corrected by selecting the right version like 9.10 or 9.20 etc depends up on the different no of projects you have on the Field Service.

One more point to remember is if you are system administrator and you make changes to the solution and try to see the changes on the MobileCRM but if you can’t that might be the security role issue.

Go back to the MobileCRM and assign the sys admin role to yourself then you should be able to see the changes.

If you don’t publish the correct Mobile Version you will run into issues like “Metadata Error”, it could be any issue  and ultimately not going to push appropriately.

Final important point is to select the correct Mobile Version before publishing as the Field Service version is different from Resco Mobile CRM.

Then you open the Mobile App and re sync the metadata and check the changes made.

I hope this helps.
For Microsoft Dynamics 365 Consultancy/Training/Support/Licensing
Contact us: https://www.gmritsolutions.co.uk
Email: admin@gmritsolutions.co.uk

Share this: