XmlResult | extensions allow developers to define the Xml serializer

In this line

change script to :

So the key is to get the proper indentation?

In that case, I would recommend taking a look at the following SO thread:

Format XML string to print friendly XML string

The key is that you need indentation, which can be achieved through the XmlTextWrite.Formatting = Formatting.Indented option.

These two lines are being executed, but not in the order you think. GlobalScope.launch() starts asynchronous operation, it does not wait for it to finish, so return xmlResult.toString() is probably executed before xmlResult.append().

I assume you tried to avoid blocking the main/UI thread. But note that your downloadURL() is still designed in the way that it needs to wait for resources to be downloaded before it can successfully return. And because this method is invoked from the UI thread, you can't avoid blocking this thread.

To solve this, you need to move the whole resource loading procedure into an asynchronous operation. That means: downloadXML(), downloadURL() and even feeding the adapter with data. Just remove your current GlobalScope.launch(), and inside onCreate() do something along lines:

The namespace URIs http://www.w3.org/2001/XMLSchema and http://www.w3.org/2001/XMLSchema-instance don't appear to be referenced in your example document. The important namespace URI is urn:ex.likeexam.com in which the NewExamResults node and all of its children reside. Try the following query instead...

The error message is telling you that somewhere in the code is trying to serialize the object, that is turn it into a string representation. This is probably in the framework you're using, and what you are thinking of as a "global variable" is actually stored between requests in some form of session, e.g. in a file on disk.

Because of the way SimpleXML is implemented, it doesn't allow this operation. The simplest workaround is to instead store the XML by calling ->asXML(), and then re-parse it when you need it with simplexml_load_string().

You'll want to do that round trip as rarely as possible, so it will be worth understanding better about how the "global variables" are actually handled by the framework so you can try to do it once on each request.

You are missing:

1. Square brackets ([]) around the attribute match conditions
2. Prefixing the attribute names with '@'
3. Adding each match condition separately

Simply loop over the nodes:

I didn't wait for your DDL and sample data population. So I created a conceptual sample for you. Please pay attention that the tables have implied relationships and they are used in the WHERE clauses.

SQL