Recurrence Pattern in Asynchronous Job Execution
You can execute asynchronous system operations one time or on a recurring basis by using a recurrence rule. Use the RecurrencePattern property to specify the recurrence rule. This property is included in the request classes of the CrmService messages that submit asynchronous jobs, such as bulk delete, or bulk detect duplicates. It is also included in the entity instances that represent asynchronous operations, such as the system job (asyncoperation) entity instance.
Use the following format to set the RecurrencePattern property.
| Recurrence pattern | Frequency of job execution |
| "FREQ=MONTHLY;" | Once a month |
| "FREQ=WEEKLY;" | Once a week |
| "FREQ=DAILY;" | Once a day |
| "FREQ=HOURLY;" | Once an hour |
Note A complete format for a recurrence rule is described in the RFC2445 Internet standard (Internet Calendaring and Scheduling Core Object Specification) that can be found at this location: http://rfc.net/rfc2445.html.
You can specify how frequently you want to repeat the recurrence rule by using an INTERVAL part of the rule. For example, to execute a job every three days, use the following format: "FREQ=DAILY;INTERVAL=3;". The INTERVAL is an optional part of the recurrence rule. If you do not specify INTERVAL, it is set to 1.
To run an asynchronous job without recurrence, set this property to a value that is specified in the RecurrencePattern property programming reference topic for a particular CrmService message request class or an entity.
To specify the start time of the job execution, use the RecurrenceStartTime property or the StartDateTime property in the CrmService message request classes or in the entity instances that represent asynchronous operations. The time is specified as CrmDateTime. If the property is not set, the start time is set to the value that is contained in the CrmDateTime.Now property.
See Also
Reference
Tasks
Other Resources
© 2009 Microsoft Corporation. All rights reserved.