SI4T is adding index data as XML to the package during rendering of an item, XML Fragment is stripped out by the storage extension during deployment. But in case of Dynamic Preview (XPM Session Preview), The storage extenstion is not executed by the Session preview odata webservice.

In a DD4T implementation, the DD4T de-serialization will fail because of the additional Indexing data XML.

Is there any fix for this situation?

1 Answer 1


The Generate Index Data TBB includes a function called IsTargetIndexed, which looks like it's intended to prevent the output from being generated when using Session Preview. It calls IsFastTrackPublishing in the TemplateBase.

Are your TBBs up to date?

  • Thanks, David, I have updated my Tbb's with the dev branch. Nov 5, 2015 at 10:29
  • 2
    Good detective work! The idea of that function IsTargetIndexed is that in future the presence of a search index might be something managed by the new Topology manager thing, so it could be used to control if SI4T should be 'activated' in the TBBs.
    – Will Price
    Nov 5, 2015 at 12:24

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.