> For the complete documentation index, see [llms.txt](https://help.tellius.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.tellius.com/whats-new/release-6.2/patch-6.2.0.6.md). # Patch 6.2.0.6 The 6.2.0.6 patch focuses on Vizpad stability and layout fidelity, with a set of refinements to how sections, charts, and pinned filters retain their size, alignment, and arrangement across saving, refreshing, and tab navigation. Together these changes make day-to-day Vizpad building and viewing more predictable and polished. ## 📈 Enhancements #### Context-aware dimension filter prefill across multi-table Business Views For Business Views that draw on multiple underlying tables, dimension filter dropdowns now resolve their available values using the context most relevant to the selected metric. This ensures the complete set of valid values appears in the filter, so filtering behaves intuitively even on the most complex Business Views. #### Reliable filter state across Custom and Master views Global and tab-level filters are now retained and kept isolated per view when switching between Custom Views and the Master View. Each view consistently reflects its own filter selections. ## 🛠️ Minor Fixes #### Vizpads - Sections & Layout 1. Refined section cloning so that a cloned section retains the original section's height and pinned filter layout, including expanded pinned filters. 2. Improved section sizing when working with pinned filters. Pinning and unpinning filters, switching pinned filters between Compact and Full mode, and saving sections with a mix of expanded and collapsed pinned filters now maintain consistent section sizing. 3. Ensured that the alignment of charts arranged within a section (including Text, KPI, and mixed chart types) is retained after saving, reloading, and switching between tabs. 4. Ensured that repositioning sections, including charts arranged inside sections, is retained after saving and reopening, so the layout consistently reflects the saved arrangement. 5. Refined expand and collapse behavior for charts in View mode, so an expanded chart can be collapsed as expected after switching between tabs. 6. Switching between tabs in a Vizpad now keeps the view anchored in place, removing the need to scroll back to the top each time a tab is opened. #### Vizpads - Filters 7. Resolved an issue with the display of an applied filter pill in the filter bar. 8. Refined filter cascading in Modern view so that cascading applies only to columns within the same dataset. 9. Ensured that Custom Views created in Classic Vizpads, including those containing Control filters, correctly display their pinned filters when opened in Modern view. 10. Improved handling of selective filters so that existing selective filter configurations are carried forward correctly and continue to behave as expected. 11. Refined how the "Greater than" filter condition handles values entered beyond the available range. Any value can be entered in the filter, while a pinned filter reflects the range of values present in the underlying dataset. 12. Ensured that conditional formatting applied to a measure against a Business View column is retained and correctly repopulated when the configuration is reopened. #### Data - Vizpad Backup 13. Improved scheduled Vizpad Backup, ensuring the background backup process completes as expected and correctly attributes ownership of the backup job. #### Embedding 14. In embedded Vizpads, resolved an issue where a configuration-related message could surface in certain embedded deployments, so embedded Vizpads load cleanly in these scenarios. #### Administration - Settings 15. Under **Settings → Identity Access → User Synchronization**, refined the Save behavior so that turning off **Groups synchronization** (or both **Users and Groups synchronization**) enables **Save**, allowing the change to be persisted. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.tellius.com/whats-new/release-6.2/patch-6.2.0.6.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.