Replace the dataset behind an existing widget, with a field-mapping step
Daxter Granlin
Today, pointing an existing widget at a different dataset only works when the new dataset has the same column structure as the old one. If the structures differ, the widget has to be rebuilt from scratch.
Requested behaviour
A replace option next to the dataset selection in the widget builder. After the new dataset is selected, a field-mapping screen opens, letting you map the old fields to the new ones — and the mapping then automatically updates everything in the widget that referenced the old fields (filters, sorting, grouping, calculated layers, conditional formatting), not just the displayed columns.
Why it matters — this is not only about switching PSA
switching from one PSA to another (e.g. ConnectWise → HaloPSA)
swapping one integrated tool for another — for example moving between CSAT tools such as Simplesat, BizRatings and SmileBack
replacing a templated dataset with a custom one
moving from one dataset or dataset version to another (e.g. a SQL-based dataset to an API-based one)
In each case the widgets themselves are unchanged in intent — only the field names behind them move. Rebuilding every widget by hand is the part that costs time.
Log In