Merge pull request #1203 from MicrosoftDocs/master

edupont04 from OPS portal: Merge from master to live

Author: edupont04

business-central/LocalFunctionality/Spain/SII-invoice-types-sales-purchase-documents.md

@@ -1,5 +1,5 @@
 ---
-    title: Overview of SII Invoice Types in Sales and Purchase Documents
+    title: SII Invoice Types in Sales and Purchase Documents
     description: Shows the output of the various types that are used for invoices and credit memos in connection with SII and how they are implemented.
 
     author: SorenGP
@@ -10,22 +10,23 @@
     ms.tgt_pltfrm: na
     ms.workload: na
     ms.search.keywords:
-    ms.date: 04/01/2020
+    ms.date: 08/27/2020
     ms.author: sgroespe
 
 ---
 # SII - Invoice and Credit Memo Types in Sales and Purchase Documents
-[!INCLUDE[d365fin](../../includes/d365fin_md.md)] supports the Spanish SII requirements for VAT reporting (Immediate Information Supply). For more information, see [Setup and user guide for electronic VAT information under SII in the Spanish version of Dynamics NAV](https://aka.ms/SIISetup).
+
+[!INCLUDE[d365fin](../../includes/d365fin_md.md)] supports the Spanish SII requirements for VAT reporting (Immediate Information Supply).  
 
 The following table shows the output of the various types that are used for invoices and credit memos in connection with SII and how they are implemented in [!INCLUDE[d365fin](../../includes/d365fin_md.md)].
 
 ## Sales Invoices
 |Type|Description|Implementation|
 |--|--|--|
 |F1|Invoice|Normal invoice|
-|F2|Simplified invoice (ticket)|Implemented as for F1, except a non-existing block is called “Contraparte” and additional nodes are called “ImporteTotal” and “Macrodato”.|
+|F2|Simplified invoice (ticket)|Implemented as for F1, except a non-existing block is called "Contraparte" and additional nodes are called "ImporteTotal" and "Macrodato".|
 |F3|Invoice issued to replace simplified invoices issued and filed|Same as Normal invoice|
-|F4|Invoice summary entry|Possible, but the XML file is same as for F1 because [!INCLUDE[d365fin](../../includes/d365fin_md.md)] does not support Summary invoices. <br /><br />Submissions will result in known error: Missing “NumSerieFacturaEmisorResumenFin” element.|
+|F4|Invoice summary entry|Possible, but the XML file is same as for F1 because [!INCLUDE[d365fin](../../includes/d365fin_md.md)] does not support Summary invoices. <br /><br />Submissions will result in known error: Missing "NumSerieFacturaEmisorResumenFin" element.|
 |R1|Corrected invoice (Error based on Art. 80.1, 80.2, and 80.6 LIVA)|Not supported. Only used for credit memos.|
 |R2|Corrected invoice (Art. 80.3)|Not supported. Only used for credit memos|
 |R3|Corrected invoice (Art. 80.4)|Not supported. Only used for credit memos|
@@ -43,15 +44,15 @@ The following table shows the output of the various types that are used for invo
 |R2|Corrected invoice (Art. 80.3)|Same as normal credit memo|
 |R3|Corrected invoice (Art. 80.4)|Same as normal credit memo|
 |R4|Corrected invoice (other)|Same as normal credit memo|
-|R5|Corrected invoice in simplified invoices|Same as normal credit memo except the block is called “Contraparte”.|
+|R5|Corrected invoice in simplified invoices|Same as normal credit memo except the block is called "Contraparte".|
 
 ## Purchase Invoices
 |Type|Description|Implementation|
 |--|--|--|
 |F1|Invoice|Normal invoice|
-|F2|Simplified invoice (ticket)|Implemented as for F1, except a non-existing block is called “Contraparte” and additional nodes are called “ImporteTotal” and “Macrodato”.|
+|F2|Simplified invoice (ticket)|Implemented as for F1, except a non-existing block is called "Contraparte" and additional nodes are called "ImporteTotal" and "Macrodato".|
 |F3|Invoice issued to replace simplified invoices issued and filed|Sames as for Normal invoice|
-|F4|Invoice summary entry|Possible, but the XML file is same as for F1 because [!INCLUDE[d365fin](../../includes/d365fin_md.md)] does not support Summary invoices. <br /><br />Submissions will result in known error: Missing “NumSerieFacturaEmisorResumenFin” element.|
+|F4|Invoice summary entry|Possible, but the XML file is same as for F1 because [!INCLUDE[d365fin](../../includes/d365fin_md.md)] does not support Summary invoices. <br /><br />Submissions will result in known error: Missing "NumSerieFacturaEmisorResumenFin" element.|
 |F5|Imports (DUA)|Same as for Normal invoice|
 |F6|Accounting support material|Sames as for Normal invoice|
 |R1|Corrected invoice (Error based on Art. 80.1, 80.2, and 80.6 LIVA)|Not supported. Only used for credit memos|
@@ -73,7 +74,9 @@ The following table shows the output of the various types that are used for invo
 |R2|Corrected invoice (Art. 80.3)|Same as normal credit memo|
 |R3|Corrected invoice (Art. 80.4)|Same as normal credit memo|
 |R4|Corrected invoice (other)|Same as normal credit memo|
-|R5|Corrected invoice in simplified invoices|Same as for normal credit memo except the block is called “Contraparte”|
+|R5|Corrected invoice in simplified invoices|Same as for normal credit memo except the block is called "Contraparte"|
+
+## See Also
 
-## See Also  
 [Spain Local Functionality](spain-local-functionality.md)
+[Setup and user guide for electronic VAT information under SII in the Spanish version of Dynamics NAV](https://aka.ms/SIISetup)  

business-central/across-business-functionality.md

@@ -1,5 +1,5 @@
 ---
-title: Business Functionality Supported by Business Central | Microsoft Docs
+title: Business Functionality Supported by Business Central
 description: Provides a feature overview of all the business functions and departments that are supported by application areas, such as Finance, Inventory, and Project Management.
 author: SorenGP
 
@@ -9,7 +9,7 @@ ms.devlang: na
 ms.tgt_pltfrm: na
 ms.workload: na
 ms.search.keywords: feature overview
-ms.date: 04/01/2020
+ms.date: 08/27/2020
 ms.author: sgroespe
 
 ---

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

@@ -1,6 +1,6 @@
 ---
-    title: Create XMLports based on XML schemas | Microsoft Docs
-    description: Use XML schemas to set yup the document exchange framework.
+    title: Use XML Schemas to Prepare Data Exchange Definitions
+    description: Use XML schemas to set up the document exchange framework.
     author: SorenGP
 
     ms.service: dynamics365-business-central
@@ -9,17 +9,15 @@
     ms.tgt_pltfrm: na
     ms.workload: na
     ms.search.keywords:
-    ms.date: 08/18/2020
+    ms.date: 09/01/2020
     ms.author: sgroespe
 
 ---
 # Use XML Schemas to Prepare Data Exchange Definitions
 
-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.  
+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.  
 
- 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.  
-
- 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).  
+ 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).  
 
  This topic contains the following procedures:  
 
@@ -29,10 +27,6 @@ To enable import/export of data in XML files through the data exchange framework
 
 - To generate a data exchange definition that is based on an XML schema  
 
-- To generate an XMLport for the file that is based on an XML schema  
-
-- To add the XMLport to your app  
-
 ## To load an XML schema file
 
 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
 > [!NOTE]  
 > 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.  
 
-### To generate an XMLport that is based on an XML schema  
-
-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.  
-
-2. Select the relevant XML schema, and then choose the **Open XML Schema Viewer** action.  
-
-3. In the **New XMLport No.** field, specify the number that the new XMLport object will be given when it is generated.  
-
-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.  
-
-5. Choose the **Generate XMLport** action, and then save the object as an .al file in an appropriate location.  
-
-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.  
+> [!NOTE]
+> 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.
 
 ## See Also
 

business-central/admin-upgrade-sales-to-cds.md

@@ -28,13 +28,12 @@ If you have already integrated [!INCLUDE[crm_md](includes/crm_md.md)] with [!INC
 2. Open the **Common Data Service Connection Setup** page, and choose the **Enable** toggle to turn on the connection.
 
    After you enable the CDS connection, the Business Central CDS Base Integration Solution is deployed to Common Data Service.
-3. Uninstall the Microsoft Dynamics 365 Business Central Integration solution from your Dynamics 365 Sales following [Uninstall or delete a solution topic](/powerapps/developer/common-data-service/uninstall-delete-solution) 
+3. Uninstall the Microsoft Dynamics 365 Business Central Integration solution from your Dynamics 365 Sales. For more information, see [Uninstall or delete a solution topic](/powerapps/developer/common-data-service/uninstall-delete-solution). 
 
-4. On the Microsoft Dynamics 365 Connection Setup page, choose the Enable toggle to turn on the connection to [!INCLUDE[crm_md](includes/crm_md.md)].
+4. On the **Microsoft Dynamics 365 Connection Setup** page, turn on the **Enable** toggle to connect to [!INCLUDE[crm_md](includes/crm_md.md)].
 
    After you enable the Sales connection, the Business Central Integration Solution is deployed to Sales. This enables integration with entities that are specific to [!INCLUDE[crm_md](includes/crm_md.md)], such as sales orders, quotes, and invoices.
-5. Choose **Redeploy Integration Solution** to install and configure the upgraded Business Central Integration Solution.
-6. On the **Sales Connection Setup** page, choose **Use Default Synchronization Setup** to initialize the integration table mappings for [!INCLUDE[crm_md](includes/crm_md.md)].
+5. On the **Sales Connection Setup** page, choose **Use Default Synchronization Setup** to initialize the integration table mappings for [!INCLUDE[crm_md](includes/crm_md.md)].
 
 ## See Also
 [Integrating with Dynamics 365 Sales](admin-prepare-dynamics-365-for-sales-for-integration.md)