Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

XML --> SOAP call different behavior #796

Closed
dkorinets opened this issue Oct 18, 2017 · 5 comments
Closed

XML --> SOAP call different behavior #796

dkorinets opened this issue Oct 18, 2017 · 5 comments
Assignees
Labels
investigate The issue requires further investigation to determine if this is a product bug

Comments

@dkorinets
Copy link

dkorinets commented Oct 18, 2017

CurrentNodeGlobal : xmlNode
CurrentNodeGlobal = <Equal>CT000004</Equal>

CurrentNodeGlobal.IsXmlText return TRUE through SOAP call.
CurrentNodeGlobal.IsXmlElement return TRUE through Local call

@StanislawStempin
Copy link

Could you please provide more context? What exactly is the code difference between SOAP call and local call in your case?

@dkorinets
Copy link
Author

dkorinets commented Oct 19, 2017

case true of 
       CurrentNode.IsXmlText :   
         Error('XmlText');
       CurrentNode.IsXmlAttribute :
         Error('XmlAttribute');
       CurrentNode.IsXmlElement : 
         Error('XmlElement');
 end;

In case of execution the code directly from web client IsXmlElement return TRUE value and that is correct in this context,
but in case of execution that code through SOAP IsXmlElement = FALSE and IsXmlText = TRUE - and that is not correct.

@StanislawStempin StanislawStempin added investigate The issue requires further investigation to determine if this is a product bug and removed input-needed labels Oct 19, 2017
@dkorinets
Copy link
Author

dkorinets commented Oct 19, 2017

In addition:
CurrentNodeGlobal = <Equal>CT000004</Equal>

procedure GetNodeName() : Text;
   begin
        exit(CurrentNodeGlobal.AsXmlElement.Name);
   end;

In case of execution the code directly from web client - NodeName(Equal) is retreaded.
In case of SOAP call error message:
"Unable to convert from Microsoft.Dynamics.Nav.Runtime.NavXmlText to Microsoft.Dynamics.Nav.Runtime.NavXmlElement."

@atoader atoader self-assigned this Jan 2, 2018
@atoader
Copy link
Contributor

atoader commented Jan 3, 2018

Could you please provide a complete snippet containing how to reproduce this issue together with a minimal XML document? As far as I understand, you have two documents from two different sources, one retrieved through a SOAP request and another from a local source. Could you check if these documents are identical? Please correct me if I misunderstood you.

@dkorinets
Copy link
Author

Cant't reproduce it with current version 11.0.19756.0-finus

@microsoft microsoft locked and limited conversation to collaborators Apr 12, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
investigate The issue requires further investigation to determine if this is a product bug
Projects
None yet
Development

No branches or pull requests

3 participants