Currently, when using the deployed Flex app URL, the Flex Header and Footer behave as global elements across all pages. However, when Flex pages are embedded into an external website, these global header/footer elements are excluded. If a user wants to create their own header, menu, or custom styling, this will require each embedded page to redundantly include its own header/menu logic. If using Custom CSS, flex requires dataparts containing this CSS to be present in each page if embedding into an external website. This consumes an excessive amount of DataParts and is inefficient.

It would be great to see Global Flex DataParts, essentially a single DataPart that can be referenced across multiple Flex pages, even when embedded externally. This would allow users to create reusable headers, footers, menus, or even centralized CSS containers, without duplicating content or burning through additional DataParts for each page.

Furthermore, while App Parameters are helpful for passing small bits of information, they currently don’t support long text in Flex. Even if they did, implementing a complex global header/menu via App Parameters would still require a new DataPart for every use case, defeating the purpose of reusability.