19. Microsoft Dynamic

Dynamics CRM is a piece of business software, made by Microsoft. It's a customer relationship management software that helps businesses manage their customer database, generate new leads, engage with their customers, and resolve customer service issues. The Microsoft Dynamic NAV adapter is defined in the Microsoft Control Board. This means that the on-cloud and on-premise variant that doesn't use the agent as the middleware is defined in the Microsoft Control Board. When the Agent should be used as the middleware for the on-premise deployment for Dynamics 365 xx, NAV, and AX then we are using the Agent Control Board and the Agent Microsoft Dynamics 365xx, NAV, and AX adapter from there. we can see that NAV can provide an Odata and soap API. Thus we can access these APIs using our soap and OData adapter. So that For 'Dynamics NAV' we can use the soap or rest adapter because 'Dynamics NAV' provides both flavors of API. Microsoft Dynamics NAV Server supports a range of different client types. This includes the Microsoft Dynamics NAV Windows client and the Microsoft Dynamics NAV Web client and two types of web services

• Direct connection from Salesforce to NAV. In this case the connection is open through the firewall directly to the NAV System. What is in front is only the reverse proxy if exist.
• Indirect connection from skyvva to NAV through the Agent. In this scenario the customer don't want to allow the direction connection to NAV due to security concern. Therefore they put the agent as the middleware in between Salesforce and NAV in the DMZ. The agent play the role of the gateway or middleware to block the direction connection from Salesforce. The connection goes only to the agent and the agent make the call to NAV using soap or rest API. To do this we provide for NAV als an adapter in agent e.g. 'Agent Microsoft Dynamics NAV'.

The name of  connector is 'Dynamics NAV'. Here are the steps he needs to follow in the configuration:

• Chose the deployment option. Do we have only on-premise? Because when it is the on-cloud deployment then it is called Dynamics 365 Business Central and thus the connector 'Dynamics 365 xx' has to use. If it is on-premise the we need to use the Agent. Here like the AX variant we need to use the Agent Microsoft NAV adapter when the user want to use the Agent as a gateway in the DMZ. So it the MS control board we configure the direction op-premise connection. If we need to use agent then we have to go to the Agent Control Board.
• Chose the authentication type e.g. i think that NAV support only the Basic Authentication
• If in step 1 on-premise is chosen then we will have the field 'Connection Destination' where the use need to enter the connection he has created in the first step in the Microsoft Control Board.
• Chose the protocol e.g. soap or rest/odata. Unlike AX we see that NAV support both API e.g. soap and rest.
• Now fill in other properties based on the protocol selection in step 3 e.g. if soap then we show the same properties as the soap adapter. If REST/OData then we show similar to the REST adapter properties.

If the protocol is soap then we use the code from the soap adapter. If it is REST/OData then we use the code from the rest adapter to make the callout to the API.

Microsoft Dynamic Nav is supporting 3 types of authentication:

• Basic: It requires a username and password.
• Web Service Key: It's a required API Key.
• Office 365 Authentication.

Adapter Screen:

Name: Name can be anything. Type: We have to select type of adapter as Microsoft dynamic NAV. Direction: Direction can be Inbound or Outbound. Status: Status should Active of adapter.