Covered in this article
Related pages
Latest Changelog
Version 1.0.2 ()
Microsoft-Dynamics-NAV-Odata component

Microsoft Dynamics NAV OData component

Microsoft Dynamics NAV is a global enterprise resource planning (ERP) solution that provides small and midsize businesses greater control over their financials and can simplify their supply chain, manufacturing, and operations.

General information

Microsoft Dynamics NAV component for the AVA platform.

Description

This is the component for working with Microsoft Dynamics NAV OData API on AVA platform.

Purpose

The component provides ability to connect to Microsoft Dynamics NAV.

Technical Notes

The technical notes page gives some technical details about AWS-S3 component like changelog and completeness matrix.

Requirements

Environment variables

Please Note: From the platform version 20.51 we deprecated the component LOG_LEVEL environment variable. Now you can control logging level per each step of the flow.

Credentials

  • Username - the name of the user who has rights to access Dynamics 365 Business Central / NAVOData, for your Dynamics 365 Business Central / NAVOData service NTLM authentication.
  • Password - the password, for your Dynamics NAVOData service NTLM authentication.
  • Service URL - the address of any acceptable URL where the Dynamics 365 Business Central / NAVOData service is located.

Triggers

This component has no trigger functions. This means it will not be accessible to select as a first component during the integration flow design.

Actions

Delete Object By Unique Criteria

Delete an existing entry with the criteria provided.

List of Expected Config fields

  • Object Type to Delete - select the type of object which you want to delete.

Expected input metadata

Input metadata is dynamically generated for specified object type. You need to set unique keys which specified in the Microsoft NAV OData metadata. For example:

  • Object type: Sales Order

  • Json schema:


{
  "Document_Type": {
    "type": "string",
    "required": true,
    "title": "Document_Type"
  },
  "No": {
    "type": "string",
    "required": true,
    "title": "No"
  }
}

You can find xml metadata using next url template: http://hostname:port/DynamicsNAV80/OData/$metadata.

Expected output metadata

Output metadata is dynamically generated for specified object type.

  • Object type: Sales Order

  • Json schema:


{
	"type": "object",
	"properties": {
		"result": {
			"type": "string"
		},
		"criteria": {
			"type": "object",
			"properties": {
				"Document_Type": {
					"type": "string"
				},
				"No": {
					"type": "string"
				}
			}
		}
	}
}

Microsoft OData