Getting an error from fromXml API when xml elements have different namespaces

[kalaiyarasiganeshalingam]

Description:
$Subject

Run the following sample to produce the error :

import ballerina/io;
import ballerina/xmldata;

// Defines a record type with annotations.
@xmldata:Namespace {
    prefix: "ns",
    uri: "http://sdf.com"
}
type Invoice record {
    RecordName xs\:id;
    Item[] purchased_item;
    @xmldata:Attribute
    string 'xmlns?;
    @xmldata:Attribute
    string status?;
};

@xmldata:Namespace {
    prefix: "xs",
    uri: "http://sdf.com"
}
type Item record {
    string itemCode;
    int item_count;
};

@xmldata:Namespace {
    prefix: "xs",
    uri: "http://sdf.com"
}
type RecordName record {
    
};

public function main() returns error? {
    xml data = xml `<ns:Invoice xmlns="example.com"
                        xmlns:ns="http://sdf.com" status="paid">?
                        <xs:id xmlns:xs="http://sdf.com">1</xs:id>
                        <purchased_item>
                            <itemCode>223345</itemCode>
                            <item_count>1</item_count>
                        </purchased_item>
                        <purchased_item>
                            <itemCode>223300</itemCode>
                            <item_count>7</item_count>
                        </purchased_item>
                    </ns:Invoice>`;
    Invoice output = check xmldata:fromXml(data);
    io:println(output);
}

Error:

error: XML type mismatch with record type: 'map<json>' value cannot be converted to 'problem_2_1:Invoice': 
                field 'xs:id' in record 'problem_2_1:Invoice' should be of type 'problem_2_1:RecordName', found '"1"'

[github-actions]

This issue is NOT closed with a proper Reason/ label. Make sure to add proper reason label before closing. Please add or leave a comment with the proper reason label now.

      - Reason/EngineeringMistake - The issue occurred due to a mistake made in the past.
      - Reason/Regression - The issue has introduced a regression.
      - Reason/MultipleComponentInteraction - Issue occured due to interactions in multiple components.
      - Reason/Complex - Issue occurred due to complex scenario.
      - Reason/Invalid - Issue is invalid.
      - Reason/Other - None of the above cases.