kx-datepicker

KX DatePicker Component

Also read kx-dashboard-core for: envelope, screen/widget wrapper, data sources, ViewState, binding patterns, actions, notifications, and the pre-flight checklist.

key: "BasicComponents" · definitionId: "15" · ComponentName: "DatePicker" · version: "v2.10.0"

This skill uses progressive disclosure: the hazards, workflow, and output checklist are here; the bulky JSON schema, picker-mode/field tables, ViewState declarations, and worked examples live in reference/. Read only the reference file relevant to your current step.

Reference Files

⚠️ Hazards — Read First

1. SelectedDate must be a ViewState binding — { "_dashboardsType": "viewstate", "value": "<vsName>" }. The type of that ViewState controls which picker is rendered (date, datetime, timestamp, timespan, month). A bare string will not work.
2. Declare the ViewState with the correct _type — the picker mode is inferred from it. Use "date", "datetime", "timestamp", "timespan", or "month".
3. Always set a non-null ViewState _default. The ViewState _default is the reliable way to set an initial date — it works regardless of whether a Data source is bound and fires before any query executes. Never use "_default": "": a null ViewState does not count as a "change" on the null → first-value transition, so dependent queries that use it as a parameter will not execute until the user picks a second date. Set a known-good date string (e.g. "2020-01-02"), or the string "LAD" when a data source is bound, so the query has a value to run with on initial load.
4. DefaultDate (LAD/FAD expressions) only activates when Data is bound. These expressions are resolved against the available dates returned by the data source. Without a Data binding, DefaultDate has no effect — set the initial value via the ViewState _default instead.
5. Data source must return kdb+ temporal types — use select distinct Date from <table> (not select Date) to avoid duplicate entries in the picker calendar. The source should return a single column of date, datetime, timestamp, month, or timespan values.
6. Data source key names are whitespace-sensitive — "AvailableDates" and "AvailableDates " are different keys. The Data binding on the component must exactly match the key declared in the data block, including any trailing spaces. Always verify both sides match.
7. definitionId is "15" — not "33" (TextInput) or "17" (Text).
8. width and labelWidth are in pixels — both are required for correct rendering; omitting them leaves the layout unsized.
9. QueryParam value uses <%vsName%> syntax — the ViewState reference in _queryParams must be written as "<%vsName%>" (plain angle brackets). Do not HTML-encode the brackets.