|
| 1 | +--- |
| 2 | +# required metadata |
| 3 | + |
| 4 | +title: Deployment guidelines for cash registers for France |
| 5 | +description: This topic provides guidance about how to enable the cash register functionality for the Microsoft Dynamics 365 Commerce localization for France. |
| 6 | +author: EvgenyPopovMBS |
| 7 | +manager: annbe |
| 8 | +ms.date: 08/10/2021 |
| 9 | +ms.topic: article |
| 10 | +ms.prod: |
| 11 | +ms.service: dynamics-365-retail |
| 12 | +ms.technology: |
| 13 | + |
| 14 | +# optional metadata |
| 15 | + |
| 16 | +# ms.search.form: |
| 17 | +audience: Developer |
| 18 | +# ms.devlang: |
| 19 | +ms.reviewer: v-chgri |
| 20 | +# ms.tgt_pltfrm: |
| 21 | +# ms.custom: |
| 22 | +ms.search.region: France |
| 23 | +ms.search.industry: Retail |
| 24 | +ms.author: josaw |
| 25 | +ms.search.validFrom: 2021-4-30 |
| 26 | +ms.dyn365.ops.version: 10.0.18 |
| 27 | + |
| 28 | +--- |
| 29 | +# Deployment guidelines for cash registers for France |
| 30 | + |
| 31 | +[!include [banner](../includes/banner.md)] |
| 32 | + |
| 33 | +This topic provides guidance about how to enable the cash register functionality for the Microsoft Dynamics 365 Commerce localization for France. The localization consists of several extensions of components. These extensions let you perform actions such as printing custom fields on receipts, registering additional audit events, sales transactions, and payment transactions in Point of Sale (POS), digitally signing sales transactions, and printing X and Z reports in local formats. For more information about the localization for France, see [Cash register functionality for France](./emea-fra-cash-registers.md). For more information about how to configure Commerce for France, see [Set up Commerce for France](./emea-fra-cash-registers.md#set-up-commerce-for-france). |
| 34 | + |
| 35 | +> [!NOTE] |
| 36 | +> This version of the Commerce cash register functionality for France is based on the [fiscal integration framework](./fiscal-integration-for-retail-channel.md). For information about the legacy digital signing sample for France, see [Deployment guidelines for cash registers for France (legacy)](./emea-fra-deployment.md). For guidelines about how to enable the fiscal integration functionality for France in existing environments that use the legacy digital signing sample, see [Migrate from legacy Commerce functionality for France](./emea-fra-fi-migration.md). |
| 37 | +
|
| 38 | +## Development environment |
| 39 | + |
| 40 | +Follow these steps to set up a development environment so that you can test and extend the localization functionality. |
| 41 | + |
| 42 | +### Enable Commerce runtime extension components |
| 43 | + |
| 44 | +#### RegisterAuditEventFrance component |
| 45 | + |
| 46 | +To enable the RegisterAuditEventFrance component, follow these steps. |
| 47 | + |
| 48 | +1. Find the extension configuration file for the Commerce runtime (CRT): |
| 49 | + |
| 50 | + - **Retail Server:** The file is named **commerceruntime.ext.config** and can be found in the **bin\\ext** folder under the Microsoft Internet Information Services (IIS) Retail Server site location. |
| 51 | + - **Local CRT on Modern POS:** The file is named **CommerceRuntime.MPOSOffline.Ext.config** and can be found under the local CRT client broker location. |
| 52 | + |
| 53 | +1. Register the CRT change in the extension configuration file, as shown in the following example. |
| 54 | + |
| 55 | + ``` xml |
| 56 | + <add source="assembly" value="Microsoft.Dynamics.Commerce.Runtime.RegisterAuditEventFrance" /> |
| 57 | + ``` |
| 58 | + |
| 59 | +#### ReceiptsFrance component |
| 60 | + |
| 61 | +To enable the ReceiptsFrance component, follow these steps. |
| 62 | + |
| 63 | +1. Find the extension configuration file for CRT: |
| 64 | + |
| 65 | + - **Retail Server:** The file is named **commerceruntime.ext.config** and can be found in the **bin\\ext** folder under the IIS Retail Server site location. |
| 66 | + - **Local CRT on Modern POS:** The file is named **CommerceRuntime.MPOSOffline.Ext.config** and can be found under the local CRT client broker location. |
| 67 | + |
| 68 | +1. Register the CRT change in the extension configuration file, as shown in the following example. |
| 69 | + |
| 70 | + ``` xml |
| 71 | + <add source="assembly" value="Microsoft.Dynamics.Commerce.Runtime.ReceiptsFrance" /> |
| 72 | + ``` |
| 73 | + |
| 74 | +#### XZReportsFrance component |
| 75 | + |
| 76 | +To enable the XZReportsFrance component, follow these steps. |
| 77 | + |
| 78 | +1. Find the extension configuration file for CRT: |
| 79 | + |
| 80 | + - **Retail Server:** The file is named **commerceruntime.ext.config** and can be found in the **bin\\ext** folder under the IIS Retail Server site location. |
| 81 | + - **Local CRT on Modern POS:** The file is named **CommerceRuntime.MPOSOffline.Ext.config** and can be found under the local CRT client broker location. |
| 82 | + |
| 83 | +1. Register the CRT change in the extension configuration file, as shown in the following example. |
| 84 | + |
| 85 | + ``` xml |
| 86 | + <add source="assembly" value="Microsoft.Dynamics.Commerce.Runtime.XZReportsFrance" /> |
| 87 | + ``` |
| 88 | + |
| 89 | +#### RestrictingShiftDuration component |
| 90 | + |
| 91 | +To enable the RestrictingShiftDuration component, follow these steps. |
| 92 | + |
| 93 | +1. Find the extension configuration file for CRT: |
| 94 | + |
| 95 | + - **Retail Server:** The file is named **commerceruntime.ext.config** and can be found in the **bin\\ext** folder under the IIS Retail Server site location. |
| 96 | + - **Local CRT on Modern POS:** The file is named **CommerceRuntime.MPOSOffline.Ext.config** and can be found under the local CRT client broker location. |
| 97 | + |
| 98 | +1. Register the CRT change in the extension configuration file, as shown in the following example. |
| 99 | + |
| 100 | + ``` xml |
| 101 | + <add source="assembly" value="Microsoft.Dynamics.Commerce.Runtime.RestrictShiftDuration" /> |
| 102 | + ``` |
| 103 | + |
| 104 | +### Enable Modern POS extension components |
| 105 | + |
| 106 | +To enable Modern POS extension components, follow these steps. |
| 107 | + |
| 108 | +1. Open the solution at **RetailSdk\\POS\\ModernPOS.sln**, and ensure that it can be compiled without errors. Additionally, confirm that you can run Modern POS from Visual Studio by using the **Run** command. |
| 109 | + |
| 110 | + > [!NOTE] |
| 111 | + > Modern POS must not be customized. You must enable User Account Control (UAC) and uninstall previously installed instances of Modern POS as required. |
| 112 | + |
| 113 | +1. In the **extensions.json** file, add the following lines to enable the extensions that must be loaded. |
| 114 | + |
| 115 | + ``` json |
| 116 | + { |
| 117 | + "extensionPackages": [ |
| 118 | + { |
| 119 | + "baseUrl": "Microsoft/Receipts.FR" |
| 120 | + }, |
| 121 | + { |
| 122 | + "baseUrl": "Microsoft/FifAuditEvent.FR" |
| 123 | + } |
| 124 | + ] |
| 125 | + } |
| 126 | + ``` |
| 127 | + |
| 128 | + > [!NOTE] |
| 129 | + > For more information, and for examples that show how to include source code folders and enable extensions to be loaded, see the instructions in the readme.md file in the **Pos.Extensions** project. |
| 130 | + |
| 131 | +1. Rebuild the solution. |
| 132 | +1. Run Modern POS in the debugger, and test the functionality. |
| 133 | + |
| 134 | +### Enable Cloud POS extension components |
| 135 | + |
| 136 | +To enable Cloud POS extension components, follow these steps. |
| 137 | + |
| 138 | +1. Open the solution at **RetailSdk\\POS\\CloudPOS.sln**, and ensure that it can be compiled without errors. |
| 139 | +1. In the **extensions.json** file, add the following lines to enable the extensions that must be loaded. |
| 140 | + |
| 141 | + ``` json |
| 142 | + { |
| 143 | + "extensionPackages": [ |
| 144 | + { |
| 145 | + "baseUrl": "Microsoft/Receipts.FR" |
| 146 | + }, |
| 147 | + { |
| 148 | + "baseUrl": "Microsoft/FifAuditEvent.FR" |
| 149 | + } |
| 150 | + ] |
| 151 | + } |
| 152 | + ``` |
| 153 | + |
| 154 | + > [!NOTE] |
| 155 | + > For more information, and for examples that show how to include source code folders and enable extensions to be loaded, see the instructions in the readme.md file in the **Pos.Extensions** project. |
| 156 | + |
| 157 | +1. Rebuild the solution. |
| 158 | +1. Run the solution by using the **Run** command, and then follow the steps in the Retail software development kit (SDK) handbook. |
| 159 | + |
| 160 | +## Production environment |
| 161 | + |
| 162 | +To create deployable packages that contain Commerce components, and to apply those packages in a production environment, follow these steps. |
| 163 | + |
| 164 | +1. In the **commerceruntime.ext.config** and **CommerceRuntime.MPOSOffline.Ext.config** package configuration files under the **RetailSdk\\Assets** folder, add the following lines to the **composition** section. |
| 165 | + |
| 166 | + ``` xml |
| 167 | + <add source="assembly" value="Microsoft.Dynamics.Commerce.Runtime.ReceiptsFrance" /> |
| 168 | + <add source="assembly" value="Microsoft.Dynamics.Commerce.Runtime.RegisterAuditEventFrance" /> |
| 169 | + <add source="assembly" value="Microsoft.Dynamics.Commerce.Runtime.RestrictShiftDuration" /> |
| 170 | + <add source="assembly" value="Microsoft.Dynamics.Commerce.Runtime.XZReportsFrance" /> |
| 171 | + ``` |
| 172 | + |
| 173 | +1. In the **extensions.json** file under the **RetailSDK\\POS\\Extensions** folder, add the following lines to enable the POS extension. |
| 174 | + |
| 175 | + ``` json |
| 176 | + { |
| 177 | + "extensionPackages": [ |
| 178 | + { |
| 179 | + "baseUrl": "Microsoft/Receipts.FR" |
| 180 | + }, |
| 181 | + { |
| 182 | + "baseUrl": "Microsoft/FifAuditEvent.FR" |
| 183 | + } |
| 184 | + ] |
| 185 | + } |
| 186 | + ``` |
| 187 | + |
| 188 | +1. Open the MSBuild Command Prompt for Visual Studio utility, and run **msbuild** under the Retail SDK folder to create deployable packages. |
| 189 | +1. Apply the packages via Microsoft Dynamics Lifecycle Services (LCS) or manually. For more information, see [Create deployable packages](../dev-itpro/retail-sdk/retail-sdk-packaging.md). |
| 190 | + |
| 191 | +## Enable the digital signature in offline mode for Modern POS |
| 192 | + |
| 193 | +To enable the digital signature in offline mode for Modern POS, you must follow these steps after you activate Modern POS on a new device. |
| 194 | + |
| 195 | +1. Sign in to POS. |
| 196 | +1. On the **Database connection status** page, ensure that the offline database is fully synchronized. When the value of the **Pending downloads** field is **0** (zero), the database is fully synchronized. |
| 197 | +1. Sign out of POS. |
| 198 | +1. Wait for the offline database to be fully synchronized. |
| 199 | +1. Sign in to POS. |
| 200 | +1. On the **Database connection status** page, ensure that the offline database is fully synchronized. When the value of the **Pending transactions in offline database** field is **0** (zero), the database is fully synchronized. |
| 201 | +1. Restart Modern POS. |
0 commit comments