Page 1 of 1
import from XML screen Bug
Posted: September 6th, 2022, 2:52 pm
by CathyC
Working with Shalom, in classic we exported a method, then in MVC tried to import. The method was called DeleteECListRecord.
When trying to import in MVC, we had just made a new method for it to overwrite. but when the widget opened, it selected a different name (delete saved cart). We didnt notice that right away and clicked "Import" and saw this blank message and if you click ok, it doesnt do anything. Like it failed some validation.
Re: import from XML screen Bug
Posted: September 6th, 2022, 5:45 pm
by SteveCap
Was the method that you want to override checked out in the project? Currently there is a bug where import will not work unless it is. There is task #10770 for this.
Re: import from XML screen Bug
Posted: September 6th, 2022, 7:51 pm
by CathyC
ah yes it was, okay thank you!
Re: import from XML screen Bug
Posted: September 21st, 2022, 5:40 pm
by shalomsims
I'm still having an issue with importing a file from XML. Before the scenario was exporting a Method. This time I am trying to export a WebPart Control from 5.1 Classic into 5.1 MVC.
I tried importing normally first and got this result. Then I created it and tried to override it and ended up with the same result.
I attached a copy of the WebPart Control I am trying import. I'm not sure if that's exactly what it's called but it is essentially like a controller called on button click. It's not inside a CallMethod currently but I want to export it as a method. If this is not the way to do that is there another way?
*Edit: I Changed the name to ImportUploadFromFile. It worked but the result of this in MVC shows me the view from 5.1 Classic. Is that normal? I've only ever imported Methods before so I don't know how it's supposed to be.
Re: import from XML screen Bug
Posted: September 22nd, 2022, 11:08 am
by SteveCap
You cannot export a classic webpage/widget and import it to use in mvc. You have to manually copy and paste any logic over. When you tried to override it failed because classic is not compatible with mvc and gave an error. When you changed the name it allowed you to import the classic webpage/widget but you will never be able to load it because it is still in classic mode and cannot be switched. I have created task #10820 to fix the error message and to not even allow you to import the classic webpage/widget.