[This is preliminary documentation and is subject to change.]

Author: Mats halfvares, the content Studio development team.

Published: 2008-11-18

Applies to: Content Studio version 5.2 and later

Type: Information

More information

In Content Studio version 5.2 a new synchronous event OnXmlIndexFieldDelete has been introduced. The idea behind this event is to make it possible to synchronize indexed xml data with an external source. Such a source can be used to provide more specialized and efficient seach capability that the xml filter queries provided by Content Studio. This event is fired every time an indexed Ept field is de-indexed thus removed from the Xml index.

An event handler for this event is implemented in the same fashion as any synchronous even handler (see the article .Creating an syncronous event handler). However, there is one special thing about this event that needs to be specifically document - the format of the passed in EPT xml content.

In the event handler's EventHandler method the content argument will contain a specially crafted xml fragment with the following syntax and meaning.

CopyXml in the content argument
<ept isdraft="" documentId="0" categoryid="12345">
    <field name="FieldName" tagId="34595" obsolete="True" />
Xml, elements and attributes
ept/@isdraftAlways an empty string.
ept/@documentIdInteger: Always zero (0).
ept/@categoryIdInteger: Specifies the numeric identifier of the Ept document's category.
ept/field/@nameString: specifies the name of the field.
ept/field/@tagIdInteger: Specifies the internal Xml index identifier of the field.
ept/field/@obsoleteBoolean: Always 'True' since the field has just been obsolete

See also

OnXmlIndexSave event data.html