Illegal XML Check

Note: This is only applicable where EEPOS stores are present.

Replication to EEPOS may fail if Illegal XML characters are present in a record. A new stored procedure in available in EEE version 1.76 and later that may be run to determine if any records in a table has an illegal XML character in one of its fields:

usp_dbm_IllegalXmlCheck

This stored procedure can only run for tables that have a single primary key field. e.g. Product, Style.

It expects two parameters:
@tableName - the name of the table to run the procedure for (as a string)
@fieldName - the name of the primary key field of the table(as a string).

E.g. to run this against the Product table, the SQL will be:

EXEC dbo.usp_dbm_IllegalXmlCheck @tableName = 'Product', @fieldName = 'ProductCode';

If any illegal XML characters are found, an email will be send to the Email addresses specified in Company Parameters with the details.

This stored procedure can also be set up to be run as an SQL Agent job for clients who would like to run this on a schedule. In order to prevent unnecessary load on the server, the first run will be for all the records in the specified table, and any subsequent runs will only consider rows that have been updated since the previous run.