You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've set up notification emails in the live integration configuration, so an email will be sent, when an error occurs. The email content could do with a bit of improvement, though :)
The log information we get here is "11/07/2024 07:07:20.529 am: ResponseError: Response is not valid XML format: 'Data at the root level is invalid. Line 1, position 1.'."
This is an exception message from the thrown buy the XML library when trying to load the XML response in to an XmlDocument object. This makes very little sense to e.g. the internal IT department at the customer who also receives these notifications.
If we look at the log file instead, there is actually a more meaningful error message:
This is an error message from the ERP system saying that the product we attempted to do a price look-up for does not exist. The customer can use this to do their own troubleshooting and won't have to worry about .net exception messages.
The log file continues with some entries of price look-up, I believe:
I don't know the relevance of this information, but if it is not relevant for the error that occurred, perhaps is should just be removed.
Br.
Lars
The text was updated successfully, but these errors were encountered:
Hi :)
We've set up notification emails in the live integration configuration, so an email will be sent, when an error occurs. The email content could do with a bit of improvement, though :)
The log information we get here is "11/07/2024 07:07:20.529 am: ResponseError: Response is not valid XML format: 'Data at the root level is invalid. Line 1, position 1.'."
This is an exception message from the thrown buy the XML library when trying to load the XML response in to an XmlDocument object. This makes very little sense to e.g. the internal IT department at the customer who also receives these notifications.
If we look at the log file instead, there is actually a more meaningful error message:
This is an error message from the ERP system saying that the product we attempted to do a price look-up for does not exist. The customer can use this to do their own troubleshooting and won't have to worry about .net exception messages.
The log file continues with some entries of price look-up, I believe:
I don't know the relevance of this information, but if it is not relevant for the error that occurred, perhaps is should just be removed.
Br.
Lars
The text was updated successfully, but these errors were encountered: