This documentation is archived and is not being maintained.

Resource Entities

banner art

[Applies to: Microsoft Dynamics CRM 4.0]

Find the latest SDK documentation: CRM 2015 SDK

Resources represent the people, tools, rooms, or pieces of equipment that are used to deliver a service. In Microsoft Dynamics CRM, resources are categorized as Users or Facilities/Equipment. Resources are collected into resource groups with similar attributes to make them easier to work with by adding the resources to a constraintbasedgroup. Upon creation, if a calendar is not specified for a resource, a calendar with 24 hours a day, seven days a week availability is created by default.

A resource is an entity that can be scheduled. Examples of resources include employees, contacts, customers, knowledge workers, or physical assets like equipment. In the Microsoft Dynamics CRM SDK, resources are represented by the systemuser and equipment classes. As resources, these entities also have a site property that can affect scheduling.

A resource also has its own calendar that defines working hours and constraints. Resources support multiple concurrent appointments. This is supported by using the capacity set in the calendar rule for a calendar. A resource calendar describes not only when a resource is not available but also describes the resource effort available (capacity) and, optionally, the effort required (service cost). This is defined on a resourcespec for services it supports. The resource specification is a required component of the service. It cannot be scheduled without specifying schedulable resources. These are evaluated by the scheduling engine when it is searching for resource availability for a particular appointment request. The resource is responsible for keeping its appointment book and responding to the scheduling engine only for existing commitments, calendar restrictions, and constraints.

Resources can be grouped together to form a pool of available resource groups for the scheduling engine to select from when conducting a search. A service may define requirements on the resource group as a whole, for example, any from the group, all from the group, or a subset. For more information, see resourcegroup and resourcespec.

A resource specification is an entity that chooses members within a group or team. It is also the link between a service and its resources and can be contained within a resource group to allow for nesting. For more information, see the diagram in the scheduling section. A resource specification defines the number and method for selecting resources within a group in addition to the effort required for a given service. Each service has exactly one resource specification but many services may share the same resource specification.

Resources can be grouped together to form a pool of available resources for the scheduling engine to select from when conducting a search. Resource groups can contain user resources, equipment resources, teams and other resource groups.

Resource groups enable the scheduling engine to select an available resource from a pool of resources. For example, one group could include all resources that have the skill of "Doctor." Another resource group could include all resources that have the skill of "Nurse." You can then define a resource specification that specifies one from the Doctors group and another that specifies two from the Nurses group. You can now define a new resource group called a "Surgery Crew," which includes these two resource specifications, one from Doctors and two from Nurses. A "Surgery" service can now refer to a resource specification that refers to this resource group. This is one example of how to quickly build a well-defined set of resource rules to participate in a service.

The following illustration shows the entity relationships for this area. For more information, see Key to Entity Diagrams.

Resource entity model

See Also


Other Resources

© 2010 Microsoft Corporation. All rights reserved.