Add data refresh capability for original tables with automatic derived table regeneration #225
+551
−38
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Users need to update base data after creating charts without losing derived transformations. Currently no mechanism exists to refresh data and propagate changes to dependent tables.
Changes
Backend (
tables_routes.py)/api/tables/refresh-derived-dataendpoint that re-executes Python transformation code in subprocess for securityFrontend (
DataThread.tsx)RefreshDataDialogcomponent supporting file upload (CSV/XLSX/JSON) or raw JSON pasteState Management (
dfSlice.tsx)updateTableRowsaction to update table data and refresh concept shelf itemsUsage
Security
Python transformations execute in subprocess with audit hooks blocking file writes and dangerous operations.
Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.