2
Hi All,
I have scenario to add a custom field in dialog view (e.g. TransferOrderInputDialog) but I can't find it in the "schema for extension manifest" (manifestSchema.json).
Is it possible to extend Dialog view? Please advise, if anyone experience the dialog extension.
Hi, if MS adds such kind of trigger, trigger itself will contain the information about transfer order transaction from dialog 1 (as trigger input parameter) - so you will be able to use it.
Hi Oksana
The business scenario is about to add transfer reason code into transfer order and transfer line. The reason code is from custom tables, because there will be different reasons of each country (there are 4 countries). Reason codes must be in option list.
MS engineer also explain alternative solution: -
"The other option is we can add post rigger to this dialog, so after the standard dialog is shown you can show custom dialogs to capture the custom fields, the drawback of this approach is the user experience, first the standard dialog will show then the custom dialog will show up. The user will not be able to enter all the details in one go but this less work because you gone add code only for your custom fields/dialogs."
Difficulties: -
1. If we pop-up 2nd (custom) dialog after saving transfer order, I don't know how to bind custom entities into option list yet.
2. In new mode, how to pass transfer order transaction from 1st dialog to 2nd (custom) dialog and save record.
2. In edit mode, how to pass transfer order transaction from datalist to custom dialog
Not too much example in Retail SDK.
Thank you for sharing the reply of Product group.
Could you, please, explain business scenario that you are trying to achieve? Maybe we could find some workaround without standard dialog extension
Hi Oksana
I requested already. This is the way he replied.
"Make the transfer order in/out dialog overridable – Extension code can override this dialog and add all the custom fields + standard fields according to your scenario and achieve the customization. The drawback of this approach its little complex, in the OOB dialog we show lot fields, make DB calls to get the stores/other details and we support search in those dialogs, if you override this dialog you have to implement all this code, so its complex but doable."
Hi, if it is not in the manifest, then there is no best practice way to extend it. You can create extensibility request in LCS portal to have such kind of extension supported in future.
Hi Xusheng
Thank for your reply. The link is about POS view, not about dialog view.
Dialog view is under "RetailCloudPos\webroot\Views\Controls". All dialogs aren't able to extended due to now reference in "RetailSDK\POS\Extensions\schemas\manifestSchema.json".
Please see below site for more details. Hope this can help you.
Share
Report
All responses (
Answers (
