When multiple Timeline controls are placed on the same model‑driven app form, default filter configurations (for example, Email‑only) are not reliably scoped per Timeline instance after solution export/import and publish. Although the configuration is valid and works correctly in the form designer, default filter metadata can be lost or applied globally across all Timeline controls during deployment. This makes it difficult to implement common UX patterns that require multiple timelines with different default views.

when more than one Timeline control exists on the same form, default filter behavior becomes inconsistent after solution export/import and publish, even though the configuration is valid and works correctly in the designer.

Observed behaviors include:

• Default filters not being applied to the intended Timeline
• Default filters being unexpectedly applied to all Timeline controls on the form