ServiceNow Microsoft Dynamics 365 Integration Guide

Architecture Overview

Implementation Steps

// Field mapping transform script for Dynamics to ServiceNow
var mapping = {
  'title': inputs.dynamics_case.title || '',
  'short_description': inputs.dynamics_case.title || '',
  'description': inputs.dynamics_case.description || '',
  'priority': mapPriority(inputs.dynamics_case.prioritycode),
  'state': mapState(inputs.dynamics_case.statecode)
};

function mapPriority(dynamicsPriority) {
  var priorityMap = {'1': '1', '2': '2', '3': '3'};
  return priorityMap[dynamicsPriority] || '3';
}

function mapState(dynamicsState) {
  var stateMap = {'0': '1', '1': '6', '2': '7'};
  return stateMap[dynamicsState] || '1';
}

// Transform script for Dynamics contact to ServiceNow user
var contact = source.getValue('fullname');
var email = source.getValue('emailaddress1');
var phone = source.getValue('telephone1');

if (email) {
  var user = new GlideRecord('sys_user');
  user.addQuery('email', email);
  user.query();
  
  if (!user.next()) {
    target.name = contact;
    target.email = email;
    target.phone = phone;
    target.active = true;
  } else {
    target.setDisplayValue('sys_id', user.sys_id);
  }
}

(function process(/*RESTAPIRequest*/ request, /*RESTAPIResponse*/ response) {
  try {
    var payload = request.body.data;
    var caseId = payload.incidentid;
    
    // Validate webhook source
    if (!validateWebhookSignature(request)) {
      response.setStatus(401);
      return;
    }
    
    var incident = new GlideRecord('incident');
    incident.addQuery('u_dynamics_case_id', caseId);
    incident.query();
    
    if (incident.next()) {
      updateExistingIncident(incident, payload);
    } else {
      createNewIncident(payload);
    }
    
    response.setStatus(200);
  } catch (e) {
    gs.error('Dynamics webhook error: ' + e.message);
    response.setStatus(500);
  }
})(request, response);

// Retry logic with exponential backoff
function callDynamicsAPI(action, retryCount) {
  retryCount = retryCount || 0;
  var maxRetries = 3;
  var backoffDelay = Math.pow(2, retryCount) * 1000;
  
  try {
    var response = action.execute();
    if (response.getStatusCode() == 200) {
      return response;
    } else if (response.getStatusCode() == 429 && retryCount < maxRetries) {
      gs.sleep(backoffDelay);
      return callDynamicsAPI(action, retryCount + 1);
    }
  } catch (e) {
    if (retryCount < maxRetries) {
      gs.sleep(backoffDelay);
      return callDynamicsAPI(action, retryCount + 1);
    }
    throw e;
  }
}

// Test script for validating integration
var testCase = {
  title: 'Test Integration Case',
  description: 'Testing ServiceNow integration',
  prioritycode: 2,
  customerid: 'test@company.com'
};

// Create test incident
var incident = new GlideRecord('incident');
incident.initialize();
incident.short_description = testCase.title;
incident.description = testCase.description;
incident.priority = '2';
var incidentId = incident.insert();

gs.info('Test incident created: ' + incidentId);

// Trigger sync flow
var flow = new sn_fd.FlowAPI();
flow.startFlow('dynamics365_incident_sync', {incident_id: incidentId});

Common Use Cases

Troubleshooting

Pro Tips

• →Implement delta synchronization by tracking last modified timestamps in both systems to avoid processing unchanged records, significantly improving performance and reducing API consumption. Create custom fields on relevant tables to store the last sync timestamp and use these values in OData filters when querying Dynamics 365, reducing data transfer volumes by up to 90% in steady-state operations.
• →Use Connection & Credential Aliases with multiple credential entries for different environments (dev, test, prod) to enable seamless promotion of integration flows across instances. Set up environment-specific connection aliases that automatically switch credentials based on the ServiceNow instance, eliminating manual credential updates during deployments and reducing configuration errors.
• →Leverage Dynamics 365 alternate keys for record matching instead of relying solely on GUIDs, as alternate keys provide more reliable synchronization when records are created in different environments. Configure composite alternate keys using business-meaningful fields like email addresses or external system IDs to enable robust duplicate detection and data consistency validation.
• →Implement comprehensive audit logging by creating custom tables that capture all integration transactions with payload details, response codes, and processing times. This audit trail is invaluable for troubleshooting, compliance reporting, and performance optimization, especially when dealing with data discrepancies between systems weeks or months after initial synchronization.
• →Configure Flow Designer subflows for common operations like field mapping and error handling to promote reusability and consistency across multiple integration flows. Create a library of reusable subflows for tasks like customer lookup, priority mapping, and status translation that can be maintained centrally and updated across all integration points simultaneously.
• →Set up proactive monitoring using ServiceNow Event Management to create events when integration failures occur, API response times exceed thresholds, or data quality issues are detected. Configure event rules that automatically create incidents for integration support teams and implement escalation procedures for critical synchronization failures that could impact business operations.

Known Limitations

• —Dynamics 365 Web API enforces service protection limits of 4,000 requests per user per 5-minute window and 20,000 requests per user per 24-hour period, requiring careful batch sizing and retry logic to avoid throttling. These limits are shared across all applications using the same user credentials, potentially causing conflicts in environments with multiple integrations or heavy API usage patterns.
• —Real-time synchronization latency can range from 30 seconds to several minutes depending on Flow Designer execution queues and Dynamics 365 webhook delivery delays, making true real-time integration challenging for time-critical processes. Consider this latency when designing business processes that depend on immediate data availability across both platforms.
• —The Microsoft Dynamics 365 spoke supports only cloud-based Dynamics 365 instances and requires a MID Server for on-premises deployments, adding infrastructure complexity and potential network connectivity challenges. On-premises integrations also require additional security considerations including firewall rules and certificate management that cloud-to-cloud integrations avoid.
• —Complex data transformations requiring multiple API calls or extensive business logic can impact Flow Designer performance and may exceed execution time limits, particularly when processing large datasets or performing complex field mappings. Consider using scheduled jobs or custom scripted solutions for heavy data processing requirements that exceed Flow Designer capabilities.
• —OAuth token management requires periodic re-authorization for long-running integrations, and Azure AD conditional access policies or multi-factor authentication requirements can complicate automated token refresh processes. Plan for manual re-authorization procedures and consider service account configurations that minimize authentication complications.

Frequently Asked Questions