Thx for the input.

Office has no 'do this or that' conditional controls at record or field level while parsing the data in, there being an IMEX=1 (ImportMixedTypes) setting against which is warned for then 'you may get unexpected results'. Unbeware, the driver second-guesses from the first 8 received records what the data type of the fields is and then assumes an answer for the remainder, but as it is, have no control over the order [would love to have a sort on ModTime], or a Not i.e. exclude a condition like Outcome = 4. There's an option to disable date value interpretation, which means the value just comes in as a value, but if first 8 are numeric, the assumption is, the rest will be too (which explains now why not getting warnings on 'In Progress' / ServerState=4... not the absent mapping but the pass assuming all will be a text value for that field :( ). If there were the ability to be more selective of what comes in, I'd subdivide all the requests to main types.... give me only PV, give me only Valid, give me only Error and then merge the individual data sets in a power query.

FTM, have set the .DisplayAlert = False > Do XmlMap query > .DisplayAlert = True, so these No Reply come in without alarm bells going off, then process the data with a function and set null = 19700101 0000 as the condition to evaluate in case of a null value i.e. then it can handle the situation and puts the 'No Reply' status label on. Amazingly, the function, though the documentation claims "You can not" can change the value of a field... it is slow though when parsing through 274K records live at this time, when the objective was to get to 10 minutes per 250x250, had it sub 12 minutes, back to 15+ minutes with that code injection.

There's ActiveX to inject an IMEX=1 into the driver controls i.e. when anticipating to getting close to the last query cycle (1097 last night) as the No Reply are at the end when using sorting=ReceivedTime, but it's an iffy solution, since at start there's indication of for instance 1095 pages, but then in that hour the script is running 30-40 and more pages can disappear or add, since data is pulled from a live system... final results are migrated off after 24 hours having sat in valid state **, and no more copies are in circulation (not a fast and stead rule). Then instead the issue shows up much earlier.

(** Just added up the validated results and the sum of active results approximates 2.5 days of valid on the RS pages, which is puzzling)

For 1-10000 results/day it's no issue, against my own account all is done in under 30 seconds no matter what I seem to bolt on as fluff with sometime 4000 active results on the RS pages

Greetings,
I see the issue that you are describing (for others here it is):

<Result>
    <AppName>oet1</AppName>
    <ClaimedCredit>0.0</ClaimedCredit>
    <CpuTime>0.0</CpuTime>
    <ElapsedTime>0.0</ElapsedTime>
    <ExitStatus>0</ExitStatus>
    <GrantedCredit>0.0</GrantedCredit>
    <DeviceId>3639918</DeviceId>
    <DeviceName>oc7811586721.ibm.com</DeviceName>
    <ModTime>1499677676</ModTime>
    <WorkunitId>131373917</WorkunitId>
    <ResultId>1598751658</ResultId>
    <Name>OET1_0004827_x3MWP_rig_77968_0</Name>
    <Outcome>0</Outcome>
    <ReceivedTime>null</ReceivedTime>
    <ReportDeadline>2017-07-20T09:07:56</ReportDeadline>
    <SentTime>2017-07-10T09:07:56</SentTime>
    <ServerState>4</ServerState>
    <ValidateState>0</ValidateState>
    <FileDeleteState>0</FileDeleteState>
</Result>

In particular, the <ReceivedTime>null</ReceivedTime> is ugly and not what should be there.

The options is that if the value doesn't exist, we could return:
<ReceivedTime/>
or we could simply skip the element if it is null.

Let me know which of those two options will work better in your script processing.

Xml Mapping is not my fav passtime and Office being pre-loaded with many surprises, it'd be a 50/50 card. I'd bet on <ReceivedTime/> but am sure interested the comments by the connoisseurs.

(So very near to a John McClane victory release)

I will remove the field if the value is not present. Should be released in the next week and I will update here. If that doesn't work well for you guys, then lets discuss further.