Document status: RELEASED
Date:
Order management dashboard
(TFS: 182289)
In order to provide data to the cloud (Order management dashboard) from on premise data source (Analysis services cube), a new Cloud Service: "Reporting Service" has been created.
Reporting service in Azure talks to Reporting service in POS Services (on premise) which again talks to the Reporting cube.
For documentation of the service / solution: https://tfs.lindbak.no/tfs/DefaultCollection/DotNetRetailSolutions/_wiki/wikis/DotNetRetailSolutions.wiki?wikiVersion=GBwikiMaster&pagePath=%2FDevelopment%2FReporting%2FReportingService%20API&pageId=243
How to set up service and tenant: https://tfs.lindbak.no/tfs/DefaultCollection/DotNetRetailSolutions/_wiki/wikis/DotNetRetailSolutions.wiki?wikiVersion=GBwikiMaster&pagePath=%2FDevelopment%2FReporting%2FReportingService%20API%2FAdding%20the%20service&pageId=248
How to set up POS Services: https://tfs.lindbak.no/tfs/DefaultCollection/DotNetRetailSolutions/_wiki/wikis/DotNetRetailSolutions.wiki?wikiVersion=GBwikiMaster&pagePath=%2FDevelopment%2FReporting%2FReportingService%20API%2FPOSServices%20configuration&pageId=245
Requirements:
POS Services 7.76.036 / Reporting v. 62
Improvements
Modules | Description |
|---|---|
Accounts receivable | Invoices from Chain Web (TFS: 185079) When fetching invoices from Chain Web, Reporting displayed "total amount" as "due amount". This has been corrected to make sure the "due amount" is shown correctly in reports and views. |
Customer order | Performance Improvement (TFS: 181710) The processing of customer orders in Reporting has been optimized to reduce the amount of time RT-job uses to process realtime data. Unknown customers in customer order (TFS: 183875) If Reporting receives a POSLog with a customer order for a customer that is not yet updated in Reporting, the "unknown" customer is still processed by the cube. This is implemented to avoid RT-job failure if we get sale on customers that are not yet updated in Reporting. |
General | Online returns (TFS:179652) When updating receipts where online return is used. We now link this article line to operatorId and not salesperson as before. This is because salesperson can be cashier from another store. When updating sales lines we use salesperson as before. Dependency on dll's in GAC (TFS: 181222) Reporting will not be dependent on entity framework dll's to be in GAC. Reporting will use dll's located in Libraries folder. This is to make sure other products such as Chain Web, LIP and Bridge who uses the same dll's are not affected. |
Loyalty | Discount on Stamp card items (TFS: 185310, 187005) Bonus calculation supports bonus rule 10. This is used to configure if stamp card items should get bonus or not. |
Sales | Discount details (TFS: 179719) Existing view pub.vSales is extended with columns for showing discount details. Support for new price channels (TFS: 182650) Reporting is updated to receive sales for two new price channels, InStore App and ShopAndGoMobile. |