The Regression suite automation tool (RSAT) is used to reduce the time and cost of UAT (user acceptance testing) of finance and operations.  UAT is typically required before you take a Microsoft application update, or before you apply custom code and configurations to your production environment. RSAT lets functional power users record business tasks by using a Task recorder and then convert the recordings into a suite of automated tests, without having to write source code. RSAT is fully integrated with Microsoft Azure DevOps for test execution, reporting, and investigation. Test parameters are decoupled from test steps and stored in Microsoft Excel files. Configuration: 1. Open RSAT application. 2. Select the Settings button in the upper right to configure RSAT. And next steps will help you to find those required fields input 3. Go to project settings of Lcs for your projects Go to Visual Studio Team Services. Here you need to mention the Azure DevOps project in the Azure DevOps site URL field. In order to do that, click on 4. Open Azure DevOps and create a new organization if there is no existing one. 5. Now create a new project as shown below  6. Now you need to set up a security token by clicking on  account info>security 7. Once you create the token, save it as you will not be able to access it again when you want to use it.  8. Once that is done, go back to the main page and create a new test plan. Name it as RSAT-TT (or you can use any name)   9. Now right-click on RSAT-TT and create a new suite you can name it ‘Demo’. Azure DevOps setup is done. 10. In the Azure DevOps site URL mention the Organization name that you setup in Azure DevOps. And in the Personal access token field paste the token that you had earlier saved. 11. Click on continue to select the project and continue, Save. 12. Now you need to deploy it to the environment  13. Next, open the Regression Suite Automation Tool, Go to settings In the Azure Dev Ops Url field copy it from the LCS Access token should be the security token you had copied. Click on Test connection so the Project name and Test plan will populate. 14. Now run VM. You will find Hostname and SOAP Hostname by going to IIS and then right-clicking on AOSService>Edit bindings. Copy both the Hostname and in Hostname and SOAP Hostname fields paste these values in step 16 15. Admin username should be the username you use to login to your environment. 16. To generate Thumbprint click on New and save at any location and then copy the generated certificate to the VM 17. Open the copied certificate and install it on the local machine at personal and Trusted Root Certification Authorities locations. Now Open the wif file in admin mode in notepad from the given location of VM In the wif file find whether CN name=127.0.0.1 exists or not. If not, copy the selected portion and paste it below the same authority block. Now add modify those lines as follows:-            <authority name=”CN=127.0.0.1″>             <keys>               <add thumbprint=”F46D2F16C0FA0EEB5FD414AEC43962AF939BD89A”/>             </keys>             <validIssuers>             <add name=”127.0.0.1″ />             </validIssuers>             </authority>  ( Note: Add thumbprint of installed Certificate in wif as shown) Final steps include Copy the thumbprint from RSAT settings (which was generated when you click on New) and paste it in wif file in your VM Then Mention the company name And Working directory Set the default browser as internet explorer Save as and ok 18. Next, Go to LCS open business process modeler and create a new Library 19. Name it as RSAT, go to edit and rename the process as required and you may add a child node to it by clicking on Add process. 20. Now go to Finance and operations, go to test recorder 21. Create a recording by clicking on create a recording and perform the operation and then click on the stop button. Name it as per your need then Save it to Lifecycle services or Save this to PC option. Click ok 22. Now go back to LCS in the project library and click on the requirement, tab check it’s syncing 23. Now Sync test cases and VSTS sync 24. Next go to Visual studio DevOps, test cases, click on Add existing 25. Then click on the run query and click on Add test case 26. Now go to regression suite automation and load the test and download test cases. select test and click on new and generate test execution parameter files 27. Then click on the edit option for the older version to edit values in excel For older version For newer version Now edit metadata for test in an excel file and save and close Now Run the test after this step, the automatic session for the test is handled by selenium where the browser will perform steps as test cases 28. Then run the test and after it’s completed successfully click on upload (Note the result as passed) POS RSAT Follow these steps to create a new recording by using the test recorder: Launch Cloud POS. Select the hamburger icon on the left pane and select Settings. Don’t sign in to Cloud POS. The sign in step must be recorded as part of the test recording flow, so you need to launch the recorder before sign in.) On the Settings page, in the Task and Test recorders section, select Open test recorder. Select Create a new recording. 4. Enter a name and description for the recording, and then select Start.The test recorder enters recording mode, and the recording session begins. The test recorder pane shows information and controls that are related to the recording session.  Perform the needed actions in the POS user interface. Download options After you end a recording session, you can download the recording by selecting Save to this PC. Upload that .axtr file in the business library. The .axtr file is saved to the local file system. You must … Continue reading Regression suite automation tool (RSAT) for D365 Finance and Operations, Commerce →

In this blog, I’m going to showcase to you the impact of the latest purchase price parameter on the item purchase price. Enable the latest purchase price for any product. So whenever new purchase order is created for a product with a specific price or different price, and in case the price of the product keeps changing in every purchase order based on the recent cost price of the item in the purchase order then the price of the item is also changing in the item master. I’m showing the example of the latest purchase in the below steps: Steps to enable the latest purchase parameter in the released products Navigate to the released products. Select the product for which you want to enable the latest purchase price. Open the purchase tab, Inside Price updated to enable the latest purchase price parameter Set the price in the product master to 50 USD (you can also set the prices through a trade agreement . ) Create a purchase order for this product Create a purchase order for this product and add this item to the purchase order lines. Set the purchase price for this product to 100 Confirm the purchase order. Post the product receipt (GRN) for this purchase order. Once it’s received, invoice the purchase order. Once this invoicing process is done, go back to the product master, and open the product for which we have enabled the latest purchase price. The price for this item is changed to the latest purchase order prices (prices changes from 50 USD to 100 USD). NOTE: Inside the manage cost tab item price, you can also see the purchase price is Overrides to 100 If you want to see the history of the fluctuation in purchase prices. You need to enable the Last price history. Steps to enable the last price history. Navigate to the inventory and warehouse parameters. Select the inventory accounting tab Enable the Last price history. So you can see the price change history in the item price. I hope this helps!

This blog explains how to configure the Microsoft Dynamics 365 Commerce Store Commerce app and applies to Microsoft Dynamics 365 Commerce version 10.0.25. The Store Commerce app in Dynamics 365 Commerce is the next-generation offering for physical stores. It combines Modern Point of Sale (MPOS) and Cloud Point of Sale (CPOS) into a single application, provides deployment choices to retailers, and helps improve performance. At the same, it retains all the functionality of MPOS and CPOS, including extensibility. Store Commerce supports local hardware stations and offline usage, and can be directly integrated with a payment terminal, printer, and cash drawer. The Store Commerce app provides commerce functionality for below first-line workers  Cashiers Sales Associates Inventory Associates Stock Clerks Store Managers Benefits of Store Commerce Store Commerce provides the benefits of both MPOS and CPOS. Performance is significantly improved. POS and extension upgrades are simplified through the Commerce sealed installer framework. Dedicated hardware station is supported. Offline deployment is supported. Application lifecycle management is simplified. Extension or independent software vendor (ISV) code that is developed for MPOS or CPOS by using the Commerce software development kit (SDK) can be reused in Store Commerce with minimal changes. Store Commerce supports two types of deployment topologies: In-app: All the components, such as Modern Point of Sale (MPOS), are deployed locally. Offline mode and local Hardware Station (HWS) are supported. Hybrid: Store Commerce renders the Cloud POS that is deployed in Commerce Scale Unit (CSU) and supports local Hardware stations. However, offline isn’t supported. There are no separate installers for the hybrid and in-app topologies. The deployment options are determined by the parameters that are passed during installation. In-app Deployment For the in-app deployment option, the application content is locally deployed in Store Commerce, just as for MPOS. To update the application content, run the latest version of the Store Commerce installer. The application content won’t be updated if you update the CSU. Therefore, you can manage the updates at individual registers. The in-app mode supports offline mode. Therefore, during installation, pass the –installoffline parameter to deploy the offline database. During offline mode (that is when there is no connectivity), the application won’t be able to connect to CSU or Commerce headquarters and will use the locally deployed CRT. Note: During the installation of Store Commerce, users can pass parameters to select either the hybrid option or the in-app option. The default option is in-app deployment. Hybrid Deployment Store Commerce is a shell that renders CPOS and connects to Headless Commerce and Commerce headquarters by using CSU in online mode. In hybrid mode, Store Commerce app content is rendered from CPOS that is hosted in CSU. When the Store Commerce app is opened, it will prompt for the CPOS URL. To update Store Commerce, just update the CSU. Store Commerce will then automatically receive the update. Because updates are centrally managed in CSU, they don’t have to be managed at individual registers. Setup and Installation Prerequisites Windows 10 version 17763.0 or later, Windows 11 (Pro, Enterprise, LTSC, and IOT Enterprise editions), or Windows Server 2019 (Standard, Essentials) Dynamics 365 Commerce (Commerce headquarters and Cloud Scale Unit) The .NET Framework version 4.7.2 or later. See Install the .NET Framework SQL Server Express, SQL Server Standard, or SQL Server Enterprise (required only for offline mode). For information on which SQL Server edition to use, see Commerce offline implementation and troubleshooting. Device setup in Commerce headquarters For Store Commerce, a new application type that is named Store Commerce has been added on the Devices page (Retail and Commerce > Channel setup > POS setup > Devices). Select this application type when you create a device for Store Commerce. Note: If the Store Commerce application type doesn’t appear on the drop-down menu, try to run the Initialize function from the General tab of the Commerce parameters page (Retail and Commerce > Headquarters setup > Parameters > Commerce parameters). Device installation from LCS Store Commerce can be downloaded from the LCS Shared asset library. On the Shared asset library page, select Retail Self-service package as the asset type, and then find the file that ends with Store Commerce. After the file has been downloaded, follow these steps to install the app. Go to the folder where you downloaded Store Commerce and open PowerShell in administrator mode. In PowerShell, find the Store Commerce installer, and pass the install parameter to install the app. To install offline components, pass the –installoffline parameter. (For example, enter Store_Commerce Installer_exe_name install –installoffline.) If you want to enable debugging mode during installation, pass the –enablewebviewdevtools parameter. Store Commerce installation parameters You can also use the help command in PowerShell to find information about all the parameters. In PowerShell, find the Store Commerce installer, and then enter Store_Commerce Installer_exe_name help install. Parameter Description installoffline Deploy the offline database. sqlservername Specify the name of the SQL Server instance that Store Commerce uses in offline mode. If you don’t specify this parameter, the installer will use a default instance. skipsqlfulltextcheck Skip validation of the SQL Full-Text Search that is required for offline deployment. trustsqlservercertificate Trust the SQL Server certificate when a connection is established to SQL Server. To help avoid security risks, you should never use this argument for production deployments. By default, the SQL Server certificate isn’t trusted. enablewebviewdevtools Enable developer tools for Store Commerce. If you don’t specify this parameter, developer tools will be enabled only if Windows Developer Mode is enabled. retailserverurl Specify the default Retail Server URL to use for Store Commerce. If you don’t specify this parameter, the user will be prompted to enter the Retail Server URL during device activation. useremoteappcontent Use the remote application content to download the Store Commerce app content from CPOS that is hosted in CSU. By default, the local application content that is deployed with Store Commerce is used. skipversioncheck Skip the validation during downgrade. skipurlcheck Skip the validation of URLs that are passed to the installer. logdirectorypath Specify the path of the log’s directory. config Specify the path of the configuration file that will be used as part of the installation. verbosity Deploy the offline database. help Show parameter information. version Show information about the app version. … Continue reading Dynamics 365 New Store Commerce App Overview, Setup, and Installation →

In this blog, I am going to showcase how to create and post statements manually in D365 retail. In Dynamics 365 Commerce, the statement posting process is used to account for the transactions that occur in POS. The statement posting process uses the distribution schedule to pull a set of POS transactions into the headquarters (HQ). Steps for creating and posting the statement. Go to Retail and Commerce > Retail and Commerce IT > Distribution schedule. In the list, find and select the desired record. Click Run now. Click OK. Go to Retail and Commerce > Inquiries and reports > Commerce Data Exchange > Upload sessions. Refresh the page. Go to Retail and Commerce > Retail and Commerce IT > POS posting > Validate store transactions. Create the statement This step identifies the store that the statement is manually created for. In the tree, select ‘Contoso Retail\Contoso Retail USA\Central\Houston’. Click Add and Ok. Go to Default dashboard. Go to Retail and Commerce > Channels > Stores > Statements. Click New. In the Store number field, enter or select a value. In the Staff/register field, enter or select a value Format for Staff/register value is Register number: Shift ID Enter the Transactional interval value. Click Calculate statement. Click Yes. In the Counted field, enter a number. Post the statement When you post a statement, sales orders and invoices are created for the sales in the statement. Cash and carry sales are aggregated onto one sales order and are invoiced for the default customer who is assigned to the store. Sales for which a customer was added to the transaction in POS generate separate sales orders and invoices, one for each unique customer. Click Post statement. Once the statement gets posted. You can check that statement in the Posted statement. Retail and Commerce > Inquiries and reports >Posted statements Hope this helps!

In this post I will show you all the different ways you can put a customer on hold in Dynamics 365 Finance and Operations Dynamics 365 Finance and Operations has standard customer management functionality that allows account receivable managers or customer account managers to put customer accounts on various types of holds. These different hold types can restrict certain transactions or completely hold the account for all transactions. There are also ways in D365 Finance and Operations that instead of putting an entire customer account on hold, you can put an individual sales order on hold. These holds can be for operational, regulatory, or for credit reasons. Steps:- Navigate to Accounts receivable > Customers > All customers. Open the customer account you want to put on hold by clicking the customer account number hyperlink. In the “Credit and collections” fast tab, click the dropdown for the “Invoicing and delivery on hold” field and select the type of hold required for the customer. There are really only 3 options for customers (“No”, “Invoice”, “All”). The other three are used only for vendors. No – This means that the customer is not on hold. So, if you want to take a customer off hold chose this value. Invoice – This hold type means that a sales order can be created but the packing slip, and invoice buttons will be disabled. This option will still allow you to post payments against the customer. You will also receive a warning message when you create the sales order letting you know that the customer is stopped for invoicing. All – If you select this option the customer is on hold for all transactions which includes, payments, sales orders, sales quotations, and invoices. When you attempt to create a transaction like a sales order you will receive an error message. You will be able to create a sales quotation but the “Send quotation” button will be disabled.

In this blog, I am going to showcase how to resolve the issue in product creation This issue is generally happening which the specific user. When a user will try to create a new customer getting the error of ‘There is no datasource in the query. Steps to resolve this issue:- Click on Settings. Select the User Options. Click on Personalization. In the Technical name column search for “Ecoresproductcreate” personalization and clear that personalization. Logout from that user and log in again and this will be resolved. hope this helps!

In this blog, I am going to showcase how to resolve the issue in purchase orders at the time of receiving. Once the purchase order is confirmed and try to receive it, you may run into the below error. This issue is happing because purchase order lines are not updated properly. When you are received the purchase order line using excel add-in, the purchase order line will not be imported properly. Use data entity in data management to import purchase order line.  Steps to resolve this issue in the purchase order. Open the purchase order. Select the purchase order line for which you are facing this issue. In the line details, Check the inventory quantity. The quantity must be there, you will face this issue because the inventory quantity is blank. If the Inventory quantity is blank, then click on the Purchase order tab and make a change request. Click on edit and update the inventory quantity, according to purchase order line quantity, and Save the purchase order. Confirm and again try to receive the Purchase order. In the receive tab, click on the product receipt. If you are facing this issue for multiple purchase order lines then cancel that Purchase order. Create a new PO and import the purchase order line with the data entity. Hope this helps!

In Dynamics 365 for Finance and Operations we have to deploy changes to environments by creating deployable packages and installing these via Lifecycle Services (LCS). This usually works pretty well, but sometimes it can fail. While doing environment update and getting error in Step 25.  Database Sync error. You can resolve this issue by performing below steps: Open environment VM, Inside VM locate the below path. Locating DBSync DbSync (syncEngine.exe) will typically be located in the following directory under the service volume: \AosService\PackagesLocalDirectory\bin Open Cmd in administartor mode and Run Command: Running DBSync Below is the template for the command to run a Full Sync. [ServiceDriveLetter]:\AOSService\PackagesLocalDirectory\bin\syncengine.exe -syncmode=”fullall” -metadatabinaries=”[ServiceDriveLetter]:\AOSService\PackagesLocalDirectory” -connect=”Data Source=[Servername];Initial Catalog=[DatabaseName];Integrated Security=False;User ID=[];Password=[]” -verbosity=”Diagnostic” > DbSync.log 2> DbSync.err Replaced with below details: [ServiceDriveLetter] = G [ServerName] = customerServer [DatabaseName] = customerAxDb [UserName] = ________            // Typically: axdbadmin [Password] = ________ After run this command, go to below path. Open  DBSync file, you will see the Output of the DBSync. Once it’s successfully Sync. Retry the deployment then this issue will resolve. Hope this help!!

There are two ways to deploy the SSRS reports in D365 for finance and operation. The first choice would be to deploy the report directly from Visual Studio. Open the Build menu, click Deploy. Alternatively, in Solution Explorer, right-click the report project and then click Deploy. In Solution Explorer, right-click the report and then click Deploy Lastly, we can deploy the reports using PowerShell. Open Windows PowerShell in Admin mode and execute the below commands as per requirement. For deploying all SSRS reportsK:\AosService\PackagesLocalDirectory\Plugins\AxReportVmRoleStartupTask\DeployAllReportsToSSRS.ps1 -PackageInstallLocation “K:\AosService\PackagesLocalDirectory” For deploying the specific reportK:\AosService\PackagesLocalDirectory\Plugins\AxReportVmRoleStartupTask\DeployAllReportsToSSRS.ps1 -Module ApplicationSuite -ReportName <ReportName> -PackageInstallLocation “K:\AosService\PackagesLocalDirectory”(Replace <ReportName> with required report name such as RetailLabel.Report or *Retail* – this will deploy all reports containing ‘Retail’ in report name)

Introduction: In this blog, we will see how to resolve HTTP Error 503 – The service is unavailable in Microsoft Dynamics 365 Finance and Operations Details:  For resolving these kinds of errors, we have 2 solutions as of now. One is to do from the front end that is LCS and the second is to do from the back-end that is from Visual Studio From LCS: Reset the IIS from the LCS. Steps: 1.     Go to LCS, login 2.     Select the respective project, full details   3.     Go to Maintain -> Restart service       4.     Select IIS and confirm it     5.     Wait till the service is being restarted                       From Visual Studio: From the back-end, open the VM and follow the below steps: 1.     Login to VM 2.     Open the Visual Studio 3.     Go to Dynamics 365 tab 4.     Click on Restart IIS Express That’s it. Build the project and go to the frontend and check the output how it looks like. Thanks for reading and stay connected with us for more updates!!! Jagdish Solanki | Senior Technical Consultant | CloudFronts Business Empowering Solutions Team “Solving Complex Business Challenges with Microsoft Dynamics 365 & Power Platform”