Terug naar Dynamics 365 CE

Dynamics 365 Customer Engagement

Data-architectuur & modellering

Tabellen, relaties en beveiliging zo ontworpen dat het systeem snel en begrijpelijk blijft terwijl het groeit.

Dynamics 365-datamodellen

Goede datamodellering is cruciaal voor schaalbare Dynamics 365-implementaties. Onze aanpak omvat:

21 tabellen
Contact → Account (parentcustomerid)Case → Account (customerid)Account → Territory (msdyn_serviceterritory)Customer Asset → Account (msdyn_account)Customer Asset → Product (msdyn_product)Customer Asset → Functional Location (msdyn_functionallocation)Agreement → Account (msdyn_serviceaccount)Agreement → Price List (msdyn_pricelist)Work Order → Account (msdyn_serviceaccount)Work Order → Work Order Type (msdyn_workordertype)Work Order → Incident Type (msdyn_primaryincidenttype)Work Order → Case (msdyn_servicerequest)Work Order → Agreement (msdyn_agreement)Work Order → Customer Asset (msdyn_customerasset)Work Order → Functional Location (msdyn_functionallocation)Work Order → Territory (msdyn_serviceterritory)Work Order → Price List (msdyn_pricelist)Work Order Incident → Work Order (msdyn_workorder)Work Order Incident → Incident Type (msdyn_incidenttype)Work Order Incident → Customer Asset (msdyn_customerasset)Work Order Service Task → Work Order (msdyn_workorder)Work Order Service Task → Work Order Incident (msdyn_workorderincident)Work Order Product → Work Order (msdyn_workorder)Work Order Product → Product (msdyn_product)Work Order Product → Warehouse (msdyn_warehouse)Work Order Service → Work Order (msdyn_workorder)Work Order Service → Product (msdyn_service)Resource Requirement → Work Order (msdyn_workorder)Resource Requirement → Territory (msdyn_territory)Bookable Resource Booking → Work Order (msdyn_workorder)Bookable Resource Booking → Bookable Resource (resource)Bookable Resource Booking → Booking Status (bookingstatus)Bookable Resource Booking → Resource Requirement (msdyn_resourcerequirement)ContactcontactcontactidPKparentcustomeridFKAccountaccountaccountidPKmsdyn_serviceterritoryFKCaseincidentincidentidPKcustomeridFKFunctional Locationmsdyn_functionallocationmsdyn_functionallocationidPKmsdyn_parentfunctionallocationFKCustomer Assetmsdyn_customerassetmsdyn_customerassetidPKmsdyn_accountFKmsdyn_productFKmsdyn_functionallocationFKPrice ListpricelevelpricelevelidPKAgreementmsdyn_agreementmsdyn_agreementidPKmsdyn_serviceaccountFKmsdyn_pricelistFKWork Order Typemsdyn_workordertypemsdyn_workordertypeidPKWork Ordermsdyn_workordermsdyn_workorderidPKmsdyn_serviceaccountFKmsdyn_workordertypeFKmsdyn_primaryincidenttypeFKmsdyn_servicerequestFKmsdyn_agreementFKmsdyn_customerassetFKmsdyn_functionallocationFKmsdyn_serviceterritoryFKmsdyn_pricelistFKWork Order Incidentmsdyn_workorderincidentmsdyn_workorderincidentidPKmsdyn_workorderFKmsdyn_incidenttypeFKmsdyn_customerassetFKIncident Typemsdyn_incidenttypemsdyn_incidenttypeidPKWork Order Service Taskmsdyn_workorderservicetaskmsdyn_workorderservicetaskidPKmsdyn_workorderFKmsdyn_workorderincidentFKWork Order Productmsdyn_workorderproductmsdyn_workorderproductidPKmsdyn_workorderFKmsdyn_productFKmsdyn_warehouseFKWork Order Servicemsdyn_workorderservicemsdyn_workorderserviceidPKmsdyn_workorderFKmsdyn_serviceFKProductproductproductidPKWarehousemsdyn_warehousemsdyn_warehouseidPKTerritoryterritoryterritoryidPKResource Requirementmsdyn_resourcerequirementmsdyn_resourcerequirementidPKmsdyn_workorderFKmsdyn_territoryFKBookable Resource BookingbookableresourcebookingbookableresourcebookingidPKmsdyn_workorderFKresourceFKbookingstatusFKmsdyn_resourcerequirementFKBooking StatusbookingstatusbookingstatusidPKBookable ResourcebookableresourcebookableresourceidPKuseridFK

De kern van Field Service: werkorders en alles errond, met de echte logische Dataverse-namen en lookups.

Ontwerp van entiteitsrelaties

  • 1:N-relaties: Parent-childrelaties met configuratie van het cascadegedrag
  • N:N-relaties: Veel-op-veelkoppelingen via relatietabellen
  • Zelfreferentie: Hiërarchische datastructuren (bijv. accounthiërarchieën)
  • Polymorfe lookups: Klant- en betreffende-velden die naar meerdere tabeltypes verwijzen

Databeveiliging & compliance

Meerlaags beveiligingsmodel met beveiligingsrollen en privileges:

  • Business units: Organisatiehiërarchie voor datasegmentatie
  • Beveiligingsrollen: Toegangscontrole op basis van privileges, op tabel- en recordniveau
  • Beveiliging op veldniveau: Gevoelige velden beschermen tegen ongeautoriseerde toegang
  • Hiërarchische beveiliging: Toegang van managers tot records van hun medewerkers
  • Audit & wijzigingen bijhouden: Naleving van dataretentie- en auditvereisten

Prestatie-optimalisatie

We passen best practices toe voor optimale systeemprestaties:

  • Indexeringsstrategie: Indexering via alternatieve sleutels en kolommen voor Quick Find/Dataverse search; vermijd voorloopwildcards en filters op berekende kolommen
  • Query-optimalisatie: Efficiënt ontwerp van FetchXML en QueryExpression
  • Asynchrone verwerking: Achtergrondtaken voor langlopende operaties
  • Caching: Strategisch gebruik van caching voor referentiedata
  • Bulkbewerkingen: ExecuteMultiple en batch-API-calls voor scenario's met hoge volumes
VorigeMaatwerk & ontwikkelingVolgendeIntegratiepatronen

Klaar om uw klantrelaties te transformeren?

Laten we bespreken hoe Dynamics 365 CE uw digitale transformatie kan ondersteunen. We helpen u graag bij het ontwerpen, bouwen en optimaliseren van uw Dynamics 365-oplossing.