A blog on Dynamics 365 for Operations – Retail
Hi Everyone,
Wishing you a Happy New Year 2022.
Its been a while since I have posted on my blog but I hope to keep some momentum going forward.
So the team at Microsoft Dynamics have been making some significant changes to the way we build customizations for Retail based on the feedback gathered from customers / partners. You can catch up with these changes by registering for the techtalks that are lined up by using the link below.
Hope this helps
-Hitesh Manglani
Upselling is one of the common requirements in Retail POS. In this post I would like to recap how this can be achieved using configuration and no code in Dynamics 365 for Operations using info codes.
Info codes is quite an old feature and I thought it would be good to recap how we can use it to achieve “Upselling”.
Lets say we want the cashier to remember to try to upsell a product B on purchase of a certain product A (association rules)- example to prompt cashier to ask customer if he or she would like to buy batteries with purchase of camera.
The first step would be to create an infocode that will show a prompt to the cashier in the Retail POS. Infocodes can be created in Dynamics 365 in the following path- Retail and Commerce-> Channel setup -> Info codes
The input type of the info code can be setup as subcode buttons.
The subcodes need to be setup as follows. Note the use of Trigger function and Trigger code in the setup.
The above setup means that on selecting Yes, the customer agrees to buy the product we are trying to upsell (batteries) and the product will be added to the transaction.
The next part of the setup involves linking this info code to the product the cashier sells in the first place to the customer (Camera). This can be done in the released products master under Commerce tab-> Set up-> Info codes.
With the above setup in backoffice and pushed to the POS (by running the 1030 job and 1040 job), the cashier will get a prompt as shown below
On clicking Yes, the upsell will be done by adding the Batteries product to the transaction.
Regards
Hitesh Manglani
End users (Operations team and Purchase) started reporting that the Purchase Order status is changing automatically without them changing anything. The environment on which this issue was reported is Platform Update 32 – 10.0.08.
The purchase order status was changing from Confirmed to Approved and when Operations tried to GRN the order it caused an error –
“Purchase order is no longer confirmed. Posting of the order has been cancelled”.
I was trying to backtrack and check what was the code deployed in the last few packages that could have caused it, but found no code that could have caused this issue.
Finally I suspected that its a bug in the standard itself. I searched LCS and found the following issue-
If you are facing the same issue, do visit the above link and subscribe to be notified for the fix
Hope this helps
-Hitesh Manglani
If you are facing any issues with your Dyn365FO excel add-in please go to below link and you have done the necessary troubleshooting
If you face the following error despite following the above troubleshooting steps, please follow the remaining steps in this blog post below to unblock.
Note: You may need to sign in if after clicking Yes a sign in prompt appears, else you should be able to use the add-in already.
Hope this helps
-Hitesh Manglani
Hi All,
I was trying to familiarize with some of the nuances of the General Ledger Parameters module in Dynamics 365 for Operations using https://mbspartner.microsoft.com/D365/CourseModules/1643
However it was difficult to understand the effect of setting the accounting rules option in the General Parameters – Ledger Accounting rules -> Financial Dimensions -> Values used for summary account.
The below link by Ludwig Reinhard was of great help to understand how this setting affects the posting on the liability summary account.
I now know another blog site that I definitely need to go through https://dynamicsax-fico.com/author/ludwigreinhard/
Hope this helps
-Hitesh Manglani
Been a while since I last posted as I was busy with upgrading our implementation from v7.1 to v10. During our upgrade from Dynamics 365 for Retail v7.1 to v10.0, one of the main issue we faced is that of Backward compatibility.
The issue occurs when trying to run v7.1 MPOS with v10.0 Retail Server, basically “Declare Start Amount”feature does not work.
On trying to declare the start amount the cashier gets the following prompt.
On trying to key in any value, the start amount results as NAN.
Reattempting to declare the start amount simply repeats the above prompts. Now this issue is serious since it prevents the closing of shift as shown in the screenshot below.
My investigation started with debugging the MPOS code and eventually the CRT code, and I found that one of the fields “StartingAmount” had been removed from crt.ShiftsView. This was causing its value to stay as undefined.
The good news is that issue is reported to Microsoft, and we are currently awaiting the fix (currently expected in v10.0.4)
-Hitesh Manglani
When trying to build the MPOS solution on my laptop, I got the below error.
Error APPX0501 Validation error. error C00CE169: App manifest validation error: The app manifest must be valid as per schema: Line 10, Column 50, Reason: —————‘ violates pattern constraint of ‘(CN|L|O|OU|E|C|S|STREET|T|G|I|SN|DC|SERIALNUMBER|Description|PostalCode|POBox|Phone|X21Address|dnQualifier|(OID\.(0|[1-9][0-9]*)(\.(0|[1-9][0-9]*))+))=(([^,+=”<>#;])+|”.*”)(, ((CN|L|O|OU|E|C|S|STREET|T|G|I|SN|DC|SERIALNUMBER|Description|PostalCode|POBox|Phone|X21Address|dnQualifier|(OID\.(0|[1-9][0-9]*)(\.(0|[1-9][0-9]*))+))=(([^,+=”<>#;])+|”.*”)))*’. The attribute ‘Publisher’ with value ————- failed to parse. Pos.App ” 1
App manifest validation error: The app manifest must be valid as per schema: Line 10, Column SO, Reason: ‘xxxx’ violates pattern constraint of ‘(CNILIOIOUIEICISISTREETITIGIIISNIDCI
((CNILIOIOUIEICISISTREETITIGIIISNIDCISERIALNUM8ERIDescriptionPostalCodeP080xI
PhoneIX21 . The attribute ‘Publisher’ with value ‘xxx’ failed to parse.
It took me a while to figure it out but this was happening because certain features in Visual Studio were not installed, the Retail SDK Handbook helped me to confirm which features were needed to be installed. After installing the highlighted features, I restarted the machine and the solution built successfully.
Hope this helps, if someone meets the same error.
-Hitesh Manglani
One of the errors I encountered recently when building the MPOS solution is the below error
“10.0.10xxx.0” is not a supported value for TargetPlatformVersion. Please change it on the Project Property page.
I learnt the reason for this after quite some time and with the help of a colleague who faced the same issue, was that , the needed version of Windows SDK was not installed on my machine.
If you get the same error just use the below link to install the right version of the Windows SDK based on the error message.
http://go.microsoft.com/fwlink/?LinkID=798187
For instance if it could be 10.0.10586.0.
Hope this helps.
-Hitesh Manglani
So here is an interesting tidbit from a recent incident in which I was supporting the customer on Dynamics 365 for Operations – Retail.
Few transactions were suddenly reported as “Missing” by the customer. The customer provided transaction details including CCTV grab along with Credit Card Slip. I started my investigation the server logs and found that the transaction id seemed be used across two transactions. This meant that the cart was not got getting cleared. In my customization I needed to access the cart information post the cart checkout and my cart clearing code was written in the PostEndTransactionTrigger.
We also logged a support ticket with MS and over time understood from MS that the MPOS is being exited by the cashier without closing the Change Due Dialog, which resulted in the PostEndTransactionTrigger not executing.
Long story short, if you are using this Trigger, make sure it contains non -critical code as it may not trigger if user exits MPOS without closing the above change due dialog.
This article is based on 7.1 Retail SDK but should be applicable to later releases too unless a fix for this has been released.
Hope this helps
-Hitesh Manglani
If you are on a MSDyn365FO 8.1 Microsoft hosted VM, you won’t have admin rights. In this case when you open the Cloud POS solution from the Retail SDK itself you get an error.
The error occurs as you do not have rights on IIS unless you run Visual Studio with Admin rights
So to get around this issue, follow the article below to resolve the issue.
https://docs.microsoft.com/en-gb/dynamics365/unified-operations/retail/dev-itpro/cloud-dev-box
Note – For step 2 you will find the aspnet.config and redirection.config files in C:\Program Files\IIS Express\config\templates\PersonalWebServer
Following the steps will make sure your Cloud POS runs on IISExpress instead of IIS and thus allowing you to to run Cloud POS and debug by attaching to iisexpress.exe.
-Hitesh Manglani
(Special thanks to my mentor Mugunthan Mani from Microsoft for this tip )
© 2023 Dynamics Journal
Theme by Anders Noren — Up ↑