Carlos López
06/18/2026, 3:17 AMAnswer Overflow
06/18/2026, 3:17 AMspotter-code
06/18/2026, 3:17 AMspotter-code
06/18/2026, 3:17 AMisCentralizedLiveboardFilterUXEnabled
- isEnhancedFilterInteractivityEnabled
- isThisPeriodInDateFiltersEnabled
but none of these provide a min/max selectable date constraint on the picker itself.
If your goal is enforcement (not just UI disable), the supported approach is to constrain data/filter logic using runtime filters or model-level logic (worksheet/view/table), so older dates are excluded from results.
javascript
import {
init,
AuthType,
LiveboardEmbed,
RuntimeFilterOp,
} from "@thoughtspot/visual-embed-sdk";
init({
thoughtSpotHost: "https://your-ts-host",
authType: AuthType.None,
});
const fiveYearsAgo = new Date();
fiveYearsAgo.setFullYear(fiveYearsAgo.getFullYear() - 5);
const yyyyMmDd = fiveYearsAgo.toISOString().slice(0, 10);
const embed = new LiveboardEmbed("#tsEmbed", {
liveboardId: "LIVEBOARD_ID",
runtimeFilters: [
{
columnName: "Date",
operator: RuntimeFilterOp.GE,
values: [yyyyMmDd], // enforce floor date in query/results
},
],
});
embed.render();
Suggestions:
- If users must never pick older dates, best practice is to enforce at data/model level too (so it cannot be bypassed).
- If you need calendar-level UX behavior (disabled years in picker), you’d need a custom host-side filter UI and then pass values into ThoughtSpot (rather than relying on native filter modal behavior).
- If you share your current filter field type (date vs datetime) and column name, I can give you the exact operator/value format for your case.
Docs:
- Liveboard view config (embed options): https://developers.thoughtspot.com/docs/Interface_LiveboardViewConfig#_iscentralizedliveboardfilteruxenabledyuichirio_ha
06/18/2026, 6:03 AMCarlos López
06/18/2026, 8:32 PMCarlos López
06/22/2026, 12:32 PM