Reporting using the SAS® Web Report Studio Key User Action Log requires well-formed XML markup


Overview

The WebReportStudio4.4_KeyActions.log file contains information about user activity such as logging on and off, opening reports and information maps, moving reports, and renaming reports. For a full list of the recorded events, see Understand Key User Action Log Output.

Reporting Using the Log

The log is formatted in XML markup, which means you can use the XML LIBNAME engine to import the log into a SAS data set. Those steps can be found in Report Events in the Key User Action Log.

However, in order to import the log in to a SAS data set, the XML markup must be well formed. Non-escaped characters such as  <, >, and & return errors similar to these:

ERROR: Unexpected or unmatched end of element tag
ERROR: Encountered during XMLMap parsing at or near line 12, column 242.
ERROR: XML describe error: Internal processing error.

This problem is most likely to occur when you open an information map with a name that includes characters that must be escaped in well-formed XML markup.

For example, if you open an information map with the name test<test, then the log contains an entry like this.

<event><javaDate>1534298023742</javaDate><date>8/14/18</date><time>9:53 PM</time><user><![CDATA[sasdemo]]>
</user><session>3</session><code>4</code><description>Open</description><report>/Shared Data/Information Maps/test<test</report></event>


The non-escaped < in the information map name causes the syntax errors.

Best Practices for Names

If you intend to use the Key User Action Log for reporting, do not use any of these characters in information map names :  ' " < > &.

Although in some cases you can use the XMLPROCESS=PERMIT option to import non-escaped characters, this option does not work in all cases.

Note: SAS Web Report Studio does not support any of the following characters in report names, folders, or templates: \ / : * ? “ ' < > | @ # &. (This list includes the reserved characters.) As a best practice, you should avoid using any of these characters in information map names. For more information, see SAS Note 62765, "Guidelines for naming information maps for use with SAS Web Report Studio."