Since I cannot reopen an issue and haven't gotten a response on #246 I'm creating this issue. The problem is the same as in #246, tested on navdocker.azurecr.io/dynamics-nav:11.0.19660.0-finus.
kvaldik
All 10 comments
Any news on this? This is a v1-blocker for us.
kvaldik
on 9 Jan 2018
Any progress with this issue?
gudrunleos
on 15 Jan 2018
Yes. I'm working on it. I will have more info hopefully today
Kungitoo
on 15 Jan 2018
The source of the issue has been found and a fix is on the way
Kungitoo
on 16 Jan 2018
This is still not working and we are running out of time :(
Tested on the build released yesterday - (navdocker.azurecr.io/dynamics-nav:11.0.20258.0-finus)
Please advice.
gudrunleos
on 23 Jan 2018
This looks like an unrelated issue to the bug for which this issue was opened for.
Is this in some code you are upgrading or some new code?
Could you please open a new issue with repro steps?
You didn't really give me much to work with...
This also looks like a platform limitation, not a language one, so I suppose this limitation was here for a while.
Kungitoo
on 23 Jan 2018
Actually this is the same code as before.
This is the error we get when we run if XMLPort.Import then (yes, there is an if .. then around it and still we get a run time error).
Should the namespace error be fixed in navdocker.azurecr.io/dynamics-nav:11.0.20258.0-finus ?
kvaldik
on 23 Jan 2018
Yes. The fix for namespaces is in. This is an unrelated error.
Is this happening when you want to do XMLPort.Import for anything or just specific xmlport?
It looks like you are invoking the method in a write transaction. Has this code worked in cside?
Kungitoo
on 23 Jan 2018
Alright, there was some mix up here. The write transaction error was associated with the XML Namespace error by mistake. I've verified that the namespace error is fixed and that the transaction error was just the structure of our code. This code was never in CSide as it's replacing old DotNet usage.
Edit:
Although it is strange to get the write error since there is no page that opens. The XMLPort just imports the data and the import should be part of the write transaction.
kvaldik
on 23 Jan 2018
Thank you very much for clearing this up @kvaldik .
I suppose that this can be closed then. If you have more issues please open a new issue
Kungitoo
on 24 Jan 2018
Related issues
worldofthenavcraft
路
3Comments
TinaMenezes
路
3Comments
malue19
路
3Comments
ThomasBrodkorb
路
3Comments
lvanvugt
路
3Comments
Most helpful comment
The source of the issue has been found and a fix is on the way