Skip to content

Datasets v2#1433

Draft
yprikhodko wants to merge 9 commits intomainfrom
datasets_v2
Draft

Datasets v2#1433
yprikhodko wants to merge 9 commits intomainfrom
datasets_v2

Conversation

@yprikhodko
Copy link
Copy Markdown
Contributor

Issue #, if available:

Description of changes:

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@yprikhodko yprikhodko marked this pull request as draft March 9, 2026 14:06
yprikhodko and others added 7 commits March 9, 2026 15:59
…1444)

When recreating a legacy dataset as a new experience dataset, existing
permissions are now captured before deletion and reapplied after creation.
If reapplication fails, the previous permissions are printed so the user
can restore them manually.
…rience datasets (#1445)

When merging a legacy dataset into a new experience dataset, top-level
RowLevelPermissionDataSet and RowLevelPermissionTagConfiguration are
moved into SemanticModelConfiguration.TableMap as
RowLevelPermissionConfiguration, since the new experience API rejects
top-level RLS attributes. ColumnLevelPermissionRules remain at the top
level as the API accepts them for both legacy and new experience.
When a dataset needs to be migrated to the new QuickSight Data Preparation
Experience, check if other dashboards also use it. If so, show a warning
listing affected dashboards and prompt the user before proceeding with the
delete/recreate migration.

- Add find_dashboards_using_dataset() to discover dashboards referencing a dataset
- Add _confirm_dataset_experience_migration() with yellow/red warning flow
- If user declines, skip dataset update (return 'skipped' sentinel)
- Update caller to suppress 'Updated dataset' message on skip
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants