[Lens][Table] Fix filtering on tables with formula columns

[nickofthyme]

Summary

Fixes a bug in the Lens Table that broke click to filter on table rows when any column is used as a formula.

Zight.Recording.2025-10-15.at.01.31.51.PM.mp4

Fixes #239170

Details

In #236673 We added column sorting to export the correct order to csv. The issue is that the formula columns create ghost columns in the datatable used to build-up the real columns. These use the id <colId>X<number> and are removed from the export so as long as the order of the real columns was correct it was fine.

However, with filtering we use the colIndex to define the column to filter.

kibana/x-pack/platform/plugins/shared/lens/public/visualizations/datatable/components/table_actions.ts

Lines 83 to 102 in c8bccc3

	export const createGridFilterHandler =
	(
	tableRef: React.MutableRefObject<Datatable>,
	onClickValue: (data: ClickTriggerEvent['data']) => void
	) =>
	(_field: string, value: unknown, colIndex: number, rowIndex: number, negate: boolean = false) => {
	const data: ClickTriggerEvent['data'] = {
	negate,
	data: [
	{
	row: rowIndex,
	column: colIndex,
	value,
	table: tableRef.current,
	},
	],
	};
	onClickValue(data);
	};

With the non-bucketed (aka Metrics) columns, we a lookup table to map the column id to the meta data including the column index of the full table, including the ghost columns. This is why this filtering was not also broken.

kibana/x-pack/platform/plugins/shared/lens/public/visualizations/datatable/components/columns.tsx

Line 62 in c8bccc3

const columnsReverseLookup = buildColumnsMetaLookup(table);

But with the bucketed columns (aka Rows), we determine the column index from the columnConfig with excludes the ghost columns. Hence the issue, we were sorting the ghost columns to the front of the array such that all the indices of the real columns would be offset by the number of ghost columns.

All that said, a simple fix would be to just sort the real columns to the start of the array and leave unknown/ghost columns to the end as their order does not matter. Alternatively, we could create a lookup similar to above to lookup the index on the full table but I don't think that is necessary if we enforce the correct order.

Ideally, we filter by passing the columnId and not the colIndex. In this way there is no ambiguity and the createGridFilterHandler has the table to lookup the correct index from the table.columns. See #239224.

Checklist

• Unit or functional tests were updated or added to match the most common scenarios
• The PR description includes the appropriate Release Notes section, and the correct release_note:* label is applied per the guidelines
• Review the backport guidelines and apply applicable backport:* labels.

Identify risks

Minimal as sorting is the only impact.

Release Notes

Fixes a bug in the Lens Table that broke click to filter on table rows when any column is used as a formula.

[markov00]

LGTM for a quick fix

[elasticmachine]

Pinging @elastic/kibana-visualizations (Team:Visualizations)

[kibanamachine]

Starting backport for target branches: 8.18, 8.19, 9.1, 9.2

https://github.com/elastic/kibana/actions/runs/18542454977

[kibanamachine]

💚 All backports created successfully

Status	Branch	Result
✅	8.18
✅	8.19
✅	9.1
✅	9.2

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation