Hello, I'm creating a site using ASP.Net Core 3.1, with IgniteUI 19.2.25 and Infragistics.Web.AspNetCore 6.19.22.
The MVC helpers for the more common controls (ComboFor, TextEditorFor) all work without a problem.
However, the helpers for NumericEditorFor, DatePickerFor, and MaskEditorFor are not generating the model field name for the hidden input tag associated with the control. When I inspect the element, the name field is missing, while it is generated for the igCombo and the igTextEditor.
Has anyone in the team had a look? If it's working for others in the same circumstances (I'm also using Razor Pages, rather than straight MVC), then at least I can try digging in to that or I can create a small example that reproduces the problem. If not, it would be great to know whether it's being looked into.
Hello Rob V,
Thank you for your feedback! We will appreciate if you can attach a runnable code sample reproducing the issue. It will both speedup investigating the matter as well as make sure we are on the same page.
Please check the Infragistics.Web.AspNetCore source code. I believe that the problem is in the Editors\EditorExtensions.cs.
The "InternalTextEditor" looks ok, but I think that the wrapper.ID and wrapper.InputName are set incorrectly for the other InternalXXXEditor methods.
They should have:
Please let me know if that change is correct, and if so when I can get a service release/hotfix.
Rob V, thank you very much for the catch!
You are correct and we are currently working on fixing that in all the components. Our next Service Release is scheduled on 24 of March 2020, however every two weeks we are producing a Bi-weekly build and could include the fix. We always suggest using Service Release builds because they pass a regression testing, however, we can deliver the fix depending on your needs.
A temporary solution can be to set the inputName property, using the client widget. Please tell me what you think and how you would like to proceed.
I implemented the workaround today by setting the InputName for the bound field and it passed testing for the implementation that I'm working on, so I can wait for the Service Release,. In the meantime, the workaround may help others facing the same issue until the SR.
Thank you once again! I've transferred your case to our internal system and associated issue #267922 with your case. You can follow its progress and I will notify you when the fix is available.