locked
Receiving INVALID_TRANSFORM error on GetThings Request RRS feed

  • Question

  • My application is receiving an error code 34 - INVALID_TRANSFORM error on a GetThings request that worked fine yesterday. I've included the request below, with the auth-token, person-id and record-id removed.

    Can anyone help me understand what this error means, and help me determine what the issue is?

    Thanks!

    Joanne

    <wc-request:request>
    <auth>
     <hmac-data algName="HMACSHA1">aLqCE9S7ISi48a5yYmYpKczVGFY=</hmac-data>
     </auth>
    <header>
     <method>GetThings</method>
     <method-version>1</method-version>
     <record-id></record-id>
    <auth-session>
     <auth-token></auth-token>
    <offline-person-info>
     <offline-person-id></offline-person-id>
     </offline-person-info>
     </auth-session>
     <language>en</language>
     <country>US</country>
     <msg-time>2014-07-08T11:45:40.135-04:00</msg-time>
     <msg-ttl>29100</msg-ttl>
     <version>0.0.0.1</version>
    <info-hash>
     <hash-data algName="SHA1">u7T0DYRivyfzo4+z0ARU/IC2Qgs=</hash-data>
     </info-hash>
     </header>
    <info>
    <group>
    <filter>
     <type-id>822a5e5a-14f1-4d06-b92f-8f3f1b05218f</type-id>
     <type-id>52bf9104-2c5e-4f1f-a66d-552ebcc53df7</type-id>
     <type-id>4b18aeb6-5f01-444c-8c70-dbf13a2f510b</type-id>
     <type-id>3b3e6b16-eb69-483c-8d7e-dfe116ae6092</type-id>
     <type-id>879e7c04-4e8a-4707-9ad3-b054df467ce4</type-id>
     <type-id>ca3c57f4-f4c1-4e15-be67-0a3caf5414ed</type-id>
     <type-id>7ea7a1f9-880b-4bd4-b593-f5660f20eda8</type-id>
     <type-id>a5033c9d-08cf-4204-9bd3-cb412ce39fc0</type-id>
     <type-id>162dd12d-9859-4a66-b75f-96760d67072b</type-id>
     <type-id>4b7971d6-e427-427d-bf2c-2fbcf76606b3</type-id>
     <type-id>464083cc-13de-4f3e-a189-da8e47d5651b</type-id>
     <type-id>22826e13-41e1-4ba3-8447-37dadd208fd8</type-id>
     <type-id>bd0403c5-4ae2-4b0e-a8db-1888678e4528</type-id>
     <type-id>cd3587b5-b6e1-4565-ab3b-1c3ad45eb04f</type-id>
     <type-id>b81eb4a6-6eac-4292-ae93-3872d6870994</type-id>
     <type-id>40750a6a-89b2-455c-bd8d-b420a4cb500b</type-id>
     <type-id>5800eab5-a8c2-482a-a4d6-f1db25ae08c3</type-id>
     <type-id>30cafccc-047d-4288-94ef-643571f7919d</type-id>
     <type-id>9366440c-ec81-4b89-b231-308a4c4d70ed</type-id>
     <type-id>92ba621e-66b3-4a01-bd73-74844aed4f5b</type-id>
     <type-id>a5294488-f865-4ce3-92fa-187cd3b58930</type-id>
     <type-id>25c94a9f-9d3d-4576-96dc-6791178a8143</type-id>
     <type-id>df4db479-a1ba-42a2-8714-2b083b88150f</type-id>
     <type-id>46d485cf-2b84-429d-9159-83152ba801f4</type-id>
     <type-id>3d34d87e-7fc1-4153-800f-f56592cb0d17</type-id>
     </filter>
    <format>
     <section>core</section>
    xml=""
     </format>
     </group>
     </info>
     </wc-request:request>


    Tuesday, July 8, 2014 4:15 PM

Answers

  • This portion looks suspect to me:

    <format>
    <section>core</section>
    xml=""
    </format>

    The format element doesn't take content so the schema validation should be failing. If the XML is actually something like <xml/> or <xml><xml/> then you shouldn't be seeing this error. Most likely there is something that is parsing the xml element with a value that is other than an empty string.


    Jeff Jones Technical Lead HealthVault Development Team

    Monday, July 14, 2014 4:28 PM

All replies

  • Interesting. I deleted a ccd.xml file (the sample that comes with the CDA Implementation Guide - so all info in it should be valid) that I had uploaded yesterday. Problem went away.

    So the question becomes, did HealthVault throw an error because that CCD document contained a data type that HealthVault doesn't handle yet? Or for some other reason?

    Tuesday, July 8, 2014 7:33 PM
  • Hi Joanne,

    Can you send the CDA document that you believe caused the problem to the hvtech alias.

    Thanks

    -Sean

    Thursday, July 10, 2014 3:52 PM
  • This portion looks suspect to me:

    <format>
    <section>core</section>
    xml=""
    </format>

    The format element doesn't take content so the schema validation should be failing. If the XML is actually something like <xml/> or <xml><xml/> then you shouldn't be seeing this error. Most likely there is something that is parsing the xml element with a value that is other than an empty string.


    Jeff Jones Technical Lead HealthVault Development Team

    Monday, July 14, 2014 4:28 PM