Skip to content

Commit 49055df

Browse files
committed
remove XMLport
Issue #415
1 parent 367d61f commit 49055df

File tree

1 file changed

+7
-24
lines changed

1 file changed

+7
-24
lines changed

business-central/across-how-to-use-xml-schemas-to-prepare-data-exchange-definitions.md

Lines changed: 7 additions & 24 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
2-
title: Create XMLports based on XML schemas | Microsoft Docs
3-
description: Use XML schemas to set yup the document exchange framework.
2+
title: Use XML Schemas to Prepare Data Exchange Definitions
3+
description: Use XML schemas to set up the document exchange framework.
44
author: SorenGP
55

66
ms.service: dynamics365-business-central
@@ -9,17 +9,15 @@
99
ms.tgt_pltfrm: na
1010
ms.workload: na
1111
ms.search.keywords:
12-
ms.date: 08/18/2020
12+
ms.date: 09/01/2020
1313
ms.author: sgroespe
1414

1515
---
1616
# Use XML Schemas to Prepare Data Exchange Definitions
1717

18-
To enable import/export of data in XML files through the data exchange framework in [!INCLUDE[d365fin](includes/d365fin_md.md)], you can use XML schemas to define which data elements you want to exchange with [!INCLUDE[d365fin](includes/d365fin_md.md)]. You perform this work on the **XML Schema Viewer** page by loading the XML schema file, selecting the relevant data elements, and then initializing either a data exchange definition or an XMLport.
18+
To enable import/export of data in XML files through the data exchange framework in [!INCLUDE[d365fin](includes/d365fin_md.md)], you can use XML schemas to define which data elements you want to exchange with [!INCLUDE[d365fin](includes/d365fin_md.md)]. You perform this work on the **XML Schema Viewer** page by loading the XML schema file, selecting the relevant data elements, and then initializing a data exchange definition.
1919

20-
When you have defined which data elements to include based on the XML schema, you can use the **Generate XMLport** action to create the XMLport object.
21-
22-
Alternatively, you can use the **Generate Data Exchange Definition** action to initialize a data exchange definition based on the selected data elements, which you then complete in the Data Exchange Framework. This creates a record on the **Posting Exchange Definition** page where you continue by defining which elements in the file map to which fields in [!INCLUDE[d365fin](includes/d365fin_md.md)]. For more information, see [Set Up Data Exchange Definitions](across-how-to-set-up-data-exchange-definitions.md).
20+
When you have defined which data elements to include based on the XML schema, you can use the **Generate Data Exchange Definition** action to initialize a data exchange definition based on the selected data elements, which you then complete in the Data Exchange Framework. This creates a record on the **Posting Exchange Definition** page where you continue by defining which elements in the file map to which fields in [!INCLUDE[d365fin](includes/d365fin_md.md)]. For more information, see [Set Up Data Exchange Definitions](across-how-to-set-up-data-exchange-definitions.md).
2321

2422
This topic contains the following procedures:
2523

@@ -29,10 +27,6 @@ To enable import/export of data in XML files through the data exchange framework
2927

3028
- To generate a data exchange definition that is based on an XML schema
3129

32-
- To generate an XMLport for the file that is based on an XML schema
33-
34-
- To add the XMLport to your app
35-
3630
## To load an XML schema file
3731

3832
1. Make sure that the relevant XML schema file is available. The file extension is .xsd.
@@ -110,19 +104,8 @@ To enable import/export of data in XML files through the data exchange framework
110104
> [!NOTE]
111105
> You can also use the **Get File Structure** function from the **Posting Exchange Definition** page, which uses the functionality of the **XML Schema Viewer** page to prefill the **Column Definitions** TastTab.
112106
113-
### To generate an XMLport that is based on an XML schema
114-
115-
1. Choose the ![Lightbulb that opens the Tell Me feature](media/ui-search/search_small.png "Tell me what you want to do") icon, enter **XML Schemas**, and then choose the related link.
116-
117-
2. Select the relevant XML schema, and then choose the **Open XML Schema Viewer** action.
118-
119-
3. In the **New XMLport No.** field, specify the number that the new XMLport object will be given when it is generated.
120-
121-
4. Make sure the relevant nodes are selected. For more information, see the [To select or clear nodes in an XML schema](#to-select-or-clear-nodes-in-an-xml-schema) section.
122-
123-
5. Choose the **Generate XMLport** action, and then save the object as an .al file in an appropriate location.
124-
125-
6. Add the .al file to your extension project in Visual Studio Code and compile the app. For more information, see [XMLport Overview](/dynamics365/business-central/dev-itpro/developer/devenv-xmlport-overview) in the developer content.
107+
> [!NOTE]
108+
> In 2019 release wave 1 and earlier versions, you could generate an XMLport that was based on the schema and then import that into your solution. This is no longer supported.
126109
127110
## See Also
128111

0 commit comments

Comments
 (0)