I suggest you...

Fix bug in JsonEncoder - cannot handle records and fields with the same name

The JsonEncoder pipeline component cannot cope with schemas that have records and field elements with the same name. Doing this:

<foo>
<foo>bar</foo>
<foo>

Where the outer foo is a record type and the inner foo is a field element, causes the inscrutable error message:

Reason: Value cannot be null.
Parameter name: key

emitted to the event log.

This is corroborated by at least one other user:

https://social.technet.microsoft.com/Forums/systemcenter/en-US/11624e47-e800-4cf9-96db-ca08468dc6ad/restjson-message-in-biztalk-2013-r2?forum=biztalkgeneral

This is a perfectly valid scenario in both XML and JSON and there is no good reason not to support it. Even if there is some obscure technical reason why not, at the very least the error message should tell you what is wrong, and the JSON schema wizard should either change the names so that it is accepted, or refuse to accept an input instance document that would generate an unacceptable schema.

4 votes
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Tom Wolverson shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    1 comment

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...

      Feedback and Knowledge Base