---
title: "MultiExcerpt and Scroll Image Map in Data Center"
canonical: "https://support.appfire.com/space/ME/289477411/MultiExcerpt%20and%20Scroll%20Image%20Map%20in%20Data%20Center"
format: markdown
---
> Macro (aura-html)

> ℹ️ Looking for information on the Cloud? [MultiExcerpt and draw.io in cloud](https://appfire.atlassian.net/wiki/x/kglLEQ).

## Caching

For a MultiExcerpt that contains a [Scroll Image Map](https://marketplace.atlassian.com/apps/253/scroll-imagemap-for-confluence?tab=overview&hosting=datacenter) macro:

- When included in a MultiExcerpt Include macro, the image sometimes renders black shapes instead of the regular image in the image link areas unless caching is disabled.
- Use the macro editor to disable caching in your MultiExcerpt Include macro.


## Page Context

In some scenarios, the included Scroll Image Map will render correctly in a MultiExcerpt Include if you enable the parameter *Use MultiExcerpt Include Page Context* in a MultiExcerpt Include macro that is used to include a Scroll Image Map macro:

![MultiExcerpt Include macro editor with page and excerpt fields](media://ef40dfca-7d51-4e5b-ab13-c1f9b3b8efe9)

If that context switch works for your MultiExcerpt Include, you may be able to leave caching enabled for that MultiExcerpt Include macro.

Some 3rd party macros (like Scroll Image Map, Draw.io) have complex markup and rendering algorithms that can be interfered with when MultiExcerpt Include uses caching to render the markup from a previous rendering request simply. The third party macro rendering may depend on the rendering context that can be lost when using caching (or when rendering using the default context, which is the context of the MultiExcerpt page instead of the MultiExcerpt Include page). The complexities are not controlled by the MultiExcerpt Include macro, which is why it can render without caching and with the ability to choose which page context to use (the original MultiExcerpt page or the MultiExcerpt Include page).