Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Service | Customer Service, Contact Center, Fie...
Suggested answer

Maybe I need a FS365 Dataverse Primer

(0) ShareShare
ReportReport
Posted on by 378

So many questions but I'll try to start as briefly as possible.

I'm convinced D365 will be a great solution we can develop for our industry (audio/video integrators, security dealers).  However, I'm struggling with how to set up the tables.

I come from some basic MS SQL programming background and think of data normalization when creating a database.  However, so far I cannot grasp the D365 Dataverse...I'm assuming partly because they created it to be as open-ended as possible for maximum flexibility no?

My world where we are coming from (plus a little of where we want to get to):

We have accounts that are basically anyone we interact with and those can be set as a specific type.  (Manufacturers, Distributors, Reps, Customers, Subcontractors, Service Providers, Friends/Family).  Those accounts have contact records 1:N associated with them containing specific data for that contact.  Contacts can have 1:N Profiles set to drive specific workflows like (this is the invoicing contact so all invoices will go to this person).

For accounts that are of the type "Customer" then they have locations 1:N for each residence they have us to service.  That location drives all key field processes, work orders, dispatching, time tracking, invoicing, asset management.

We add Products to a work order and once that work order is complete and invoiced the product moves to the list of Assets for that location.

Dataverse Confusion

1.  In Field Service 365 I don't see a way to designate an "Account Type".  Do I just need to create a custom field for this?

I see Functional Locations but it's a bit confusing.  If I have 1000 customers and I create an FL for each of them called Main Residence and put the address, then when I search to add a FL to a WO, 1000 "Main Residence" will effectively pop in the list...image below to see what I'm seeing.

0652.Functional-Location.jpg

  • Suggested answer
    RE: Maybe I need a FS365 Dataverse Primer

    1. The relationship type field is on the account entity and should be on the form. If it isn't there you can always add back.

    Relationship-Type.png

    2. For functional location, by default it does not only show filtered by billing account. That will only happen if you modify the filter on the form property. It will filter by service account and is auto set when you choose an asset, but there are many options to open that up. Details are explained here - https://youtu.be/UCjyEKH0qFg

    2b. This is very much scenario driven. Some organizations focus on residential customers only, in this case, they may ONLY have a service account and not use the functional location at all when it is always 1 to 1. However, if you have scenarios where there are many locations for a single account, such as a campus, office building, apartment complex, etc, that's where you should use functional locations. I would recommend watching the youtube link pasted above as we discuss when to use functional locations. Conceptually, billing account is who pays the bill. Service account is the entity that requests service and is responsible to see it through to make sure it was done correctly. Usually you send reports to someone from this entity when the work order is complete, or if you need to get approvals. Functional location represents the physical space where the work is performed. You may have service service and billing accounts for a location over time but want to keep all that history when the location (tenant changes in a retail space for example). 

  • crham Profile Picture
    crham 378 on at
    RE: Maybe I need a FS365 Dataverse Primer

    1.  I don't see "Relationship Type" in the Account Summary page.

    2.  I understand your answer about setting the FL only show based on billing account but.

    2a.  I will need to think about that and make sure that nothing will break that

    2b.  I was really asking something else first.  IS IT NORMAL OR MAYBE COMMON TO HAVE MY SCENARIO WHERE BASICALLY EVERY CUSTOMER ACCOUNT WILL HAVE A FUNCTIONAL LOCATION RECORD CREATED AND ASSOCIATED?  It seems like that's not really how the database was designed and I wish to keep with good best practices.

  • RE: Maybe I need a FS365 Dataverse Primer

    Hi Partner,

    Can you click Yes under "Did this answer your question?" to close this thread if my answer is helpful.

     pastedimage1639729654897v1.png

    Thanks in advance!:)

  • Suggested answer
    RE: Maybe I need a FS365 Dataverse Primer

    Hi crham,

    1."In Field Service 365 I don't see a way to designate an "Account Type". "

    Account in Field Service can show type in the form, do you want to show account type in the work order form?

    pastedimage1639537880681v1.png

    If so, you need create a custom field to store it, or add quick view form which includes account type field from account entity based on the Service Account/Billing Account.

    2.For FL in WO, you can set it as following screenshot, which can only show FL based on the Billing Account.

    pastedimage1639475104413v1.png

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Daivat Vartak – Community Spotlight

We are honored to recognize Daivat Vartak as our March 2025 Community…

Announcing Our 2025 Season 1 Super Users!

A new season of Super Users has arrived, and we are so grateful for the daily…

Kudos to the February Top 10 Community Stars!

Thanks for all your good work in the Community!

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 292,516 Super User 2025 Season 1

#2
Martin Dráb Profile Picture

Martin Dráb 231,436 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans