In a large XML message being sent (i.e. a sql snapshot) the XML can be so long when you click Contents or open it up via the message it will time out the portal.
I.E. viewing EnsLib.SQL.Snapshot with 8733 rows
This is two suggestions: either:
1) the load of contents if it is longer than a period of time it should still load a visual trace but say something along the lines of "Contents taking a long time to load- do you want to continue to load" giving the user the option to load it into the trace
2) Perhaps limit the amount of the XML returned to the message contents tab with a "Show more" button . Something along the lines as a "Truncated for display" . Maybe it should just be on EnsLib.SQL.Snapshot
Thank you for submitting the idea. The status has been changed to "Future consideration".
Stay tuned!
Mark OReilly, thank you for your idea. You have a question on it, please answer the question to help your idea to be promoted.
In fact there is a limit implemented/enforced in the content tab end a developer community member....complained about that limit! :)
Good new is that the limit can be changed, see this post in developer community for details.
Are you experiencing this issue using specific request/response classes or maybe in an old product version?