Exporting Custom Fields via API Returns Incorrect 'XML Parsing Error' Response in Instantis EnterpriseTrack (Doc ID 2225977.1)

Last updated on JANUARY 24, 2017

Applies to:

Instantis EnterpriseTrack - Version 16.1.2.1 and later
Instantis EnterpriseTrack Cloud Service - Version 16.1.2.1 and later
Information in this document applies to any platform.

Symptoms

When attempting to export custom fields via API Project Search Custom Fields are returning an incorrect response; an example similar to below:

"XML Parsing Error: not well-formed
Location: [Server URL]?request_data=UTF-8MMM/dd/yyyyen16.1searchprojectxml|Project IDxxxxx&request_format=xml
Line Number 2, Column 13529:"

The issue can be reproduced at will with the following steps:

  1. Connect to API from browser using <Server URL>

  2. Run the following, for example (authentication key will be different)

    [Server URL]?request_data=encoding="UTF-8"?>

    <global_properties>
    <char_set>UTF-8
    <date_format>MMM/dd/yyyy
    en
    <api_version>16.1

    <request_data>
    <request_type>search
    <entity_type>project
    <output_format>xml
    <value_delimiter>|

    <app_data>

    <project_number>
    <display_name>Project ID
    XXXX

    &request_format=xml

  3. XML Parsing Error: not well-formed
    Location:
    [Server URL]?request_data=UTF-8MMM/dd/yyyyen16.1searchprojectxml|Project IDxxxxx&request_format=xml
    Line Number 2, Column 13529:

Changes

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms