Throughout my support and maintenance activities for customers, a common request is to look into notifications in CRM that are “not being sent”. There are a lot of components and configuration items involved in the process of having CRM send out messages via email. This blog focuses on some of the most common user-account-related issues that Microsoft Dynamics CRM Pending Emails. Microsoft CRM (46) Customization (37) Dynamics CRM Certification (9) CRM 2011 (8) Plug-in (8) XRM (8) CRM 4.0 Vs CRM 2011 (5) Dynamics CRM Training (5) CRM outlook client (4) PDC 09 (3) JavaScript (2) MSDN Blog (1) Microsoft Dynamics CRM online (1) Office 365 (1) Unsupported (1) Whitepaper (1) integration (1). Sep 20, 2016 My name is Nick Doelman. I am a Microsoft Business Applications MVP and I have been working with the Power Platform and Dynamics 365 since version 1.0. I am currently a Power Platform and Dynamics 365 Freelance consultant, trainer, blogger and speaker. This blog is mostly about the Power Platform and Dynamics 365 (formally known as CRM).

This topic is for administrators and developers with administration access rights in Microsoft Dynamics.

This topic describes how to troubleshoot and maintain the Microsoft Dynamics CRM integration for Episerver Campaign. The following is included:

• Checking workflows for activity and errors.
• Common error messages.
• Reducing storage space used by the integration.
• Managing divergent time stamps.
• Service updates for Microsoft Dynamics 365 Online

Checking workflows for activity and errors

Active and running workflows are shown in the CRM settings under System jobs. You can apply a filter for the Episerver Campaign workflows under Entity. There are these categories:

Microsoft Dynamics Crm Error Messages List

• APIStands for 'application programming interface'. The API specifies how some software components should interact with each other, such as accessing a database or computer hardware, or easing the work of programming graphical user interface components. APIs often are in the form of a library that includes specifications for routines, data structures, object classes, and variables. See also: https://world.episerver.com/documentation/class-libraries/ data
• Recipient Packages
• Mapping

Regularly check the Client and Recipient Packages workflows for errors. See Workflow error messages.

Do the following to check workflow activity for a client:

1. In Microsoft Dynamics CRM, open the settings and click Clients under Episerver Campaign.
2. Double click the client. The following is under Information, providing the time of the last data import:
   • Last clicks date.
   • Last opens date.
   • Last responses date.
   • Last unsubscribes date.
   • Date of last bounce limit overruns.

   If one or more imports were done more than an hour ago, the workflow is no longer active. This can be due to insufficient resources within the CRM, or a network problem.

3. Click Run Workflow and select the workflow to restart. If the problem persists after restart, contact your system administrator.

Viewing workflow error messages

If a workflow did not run successfully, Status Reason under Settings > System > System Jobs shows the message Failed.

1. Click the name of the corresponding system job to see a detailed description of the error.
2. Resolve the error.
3. If you are unable to resolve the error, click Details to see the trace for the workflow.
4. Copy the trace text and error message with the time stamp for the error, and contact customer support providing the information.

Common error messages

Reducing used disk space

Reducing used disk space is optional. The integration operation will not be affected if this is not done. However, you will save storage resources and have a better overview of workflows.

The following options are available:

• Delete recipient packages no longer required.
• Delete completed workflow jobs.

Deleting recipient packages no longer required

1. Open Microsoft Dynamics CRM and select Settings > Recipient Packages.
2. Click the arrow next to Active Episerver CampaignRecipient Packages.
3. In the drop-down list, select Old Episerver Campaign Recipient Packages.
4. Select the recipient package to delete and click Delete.

Deleting completed workflow jobs

By default, Microsoft Dynamics keeps completed workflow jobs. To configure automatic deletion of completed workflow jobs, do the following:

Microsoft Dynamics Crm Careers

1. Open Microsoft Dynamics CRM and select Settings > Processes.
2. Click the arrow next to the title.
3. In the drop-down list, select the corresponding option, such as Activated Processes.
4. Click the workflow for which the job should be automatically deleted after completion.
5. Under Workflow Job Retention, select Automatically delete completed workflow jobs (to save disk space).

   To select the check box you may have to deactivate the workflow for a short period. When you have selected the check box, reactivate the workflow.

6. Click Close.

Managing divergent time stamps

The behavior of the date fields in Microsoft Dynamics CRM can lead to divergent time stamps in CRM and Episerver Campaign. When using date fields with time specifications, use the User Local field type, as this will consider the time zone set for the user during data synchronization.

Do the following to check the data format in the field settings:

1. In Microsoft Dynamics CRM, locate the affected date and time field.
2. Edit the field, and check the properties to see if the field is defined as User Local.

   If the field is defined as Time-Zone Independent, it will not consider the time zone set in CRM. Episerver Campaign, will convert the time for display to the time zone of the user, so that deviations may occur.

   Once the field has been saved in CRM as Time-Zone Independent, it can no longer be changed. In this case, the field should be deleted and recreated.

   Service updates for Microsoft Dynamics 365 Online

   Microsoft releases service updates for Microsoft Dynamics 365 Online on different times without an announcement. Service updates might affect the functionality of the Microsoft Dynamics CRM integration for Episerver Campaign. Episerver cannot exclude possible malfunctions in advance. For more information about service updates, see Microsoft Support.

Auto Save Form Enable/Disable Microsoft Dynamics CRM 2013

Posted on Updated on

Dynamics CRM 2013 Comes up with Auto Save Functionality.
Auto save enables automatic save of records at fixed short interval for update without the need for you to explicitly click on “Save” button every time. Now you don’t need to worry about saving record when you are working on a record for a long time. In this blog we are going to discuss more about this.

Auto save of records not only saves an extra click but also reduces chances of data loss in case of any connectivity issues because now all changes in form will be automatically saved in every 30 seconds. If no changes are made on form than automatic save will not occur.

The field that someone is currently editing isn’t included in an auto-save. If someone else has updated the same record while you’re editing it, those changes will be retrieved and displayed in the form when auto-save occurs.

Microsoft Dynamics Crm Error Messages Examples

During the save, if there are any validation failures, such as invalid data, or missing required fields, etc. that prevent the save, then an error message will show at footer panel below and the auto save will not proceed.

In CRM by default this feature is turned on for all new and updated organizations. Please note that this is applicable only when updating records. If you are creating a new record then you must explicitly save the record. It will not be auto saved. Auto save capability is not applicable to Quick Create forms or Mobile forms. Also, auto save only applies to the Main form. It is also important to note that this feature is only enabled for entities with the updated user experience forms.

Reference: http://blogs.msdn.com/b/crm/archive/2013/10/15/manage-auto-save.aspx

There can be a lot of requirements for restricting auto save for any form where workflow or plugin needs to be called on save, for such kind of requirement there is no need of auto save functionality. To change the settings follow the walk-through:

1. Go to Settings
2. Go to Administration
3. Go to System Settings
4. On General tab, enable auto save on all forms click on “No”.