Troubleshooting XML data

General Profile Sources is a great way to manage your users within Interact, but there can be a few hiccups along the way.

The first thing the API endpoint does is validate the XML data against the schema. If the data file does not pass the validation process then the API will return a relevant error message. This means that the response from the API usually provides a good error message that should direct you on where to look for problems in the XML.

We would advise that, before sending the XML file to your Interact instance, you validate the XML file against the schema yourself. This will potentially help to resolve a number of validation problems before sending the data file to Interact.

The text below shows an error response from the API

{
  "Message":"The request is invalid.",
  "ModelState":{
    "UMILogicError":["The file is invalid compared to the schema. The element 'users' has incomplete content. List of possible elements expected: 'user'."]
  }
}

The JSON here has a ModelState.UMILogicError with the error text that describes the actual error. If you're using PowerShell script to implement this then the display on the screen isn't quite as nice but it still shows the relevant messages.

Listed below is some common errors we've seen with customers producing the XML and what to do to resolve the problem