MS-997 Reset local records when sync partitioning changes

[luhmirin-s]

JIRA ticket
Will be released in: version

Root cause analysis (for bugfixes only)

First known affected version: 2025.1.0

• When sync partitioning changes in the project configuration, already downloaded records remain in the local database, causing a mismatch in numbers.
• Additional local records might also affect the matching speed and results by returning records that shouldn't have been synced (if the ID pool type does not match sync partitioning).

Notable changes

• On the project configuration sync, if the change in sync partitioning has been detected, all local records are wiped, and a new sync is scheduled.
• Change of sync partitioning is an extraordinary circumstance, and some disruption should be expected. Creating more complex diff handling is possible, but the ROI would not be justify it.

Testing guidance

• Create/configure a project with project sync scope and some records.
• Log into SID and sync the records.
• Change sync scope to modules and re-add known module names in Vulcan.
• Open the SID dashboard settings and sync configuration.
• Go to Sync Info and select some modules to down sync.
• Check that the number of records in synced modules matches "Total on device".

Testiny case

Additional work checklist

• Effect on other features and security has been considered
• Design document marked as "In development" (if applicable)
• External (Gitbook) and internal (Confluence) Documentation is up to date (or ticket created)
• Test cases in Testiny are up to date (or ticket created)
• Other teams notified about the changes (if applicable)

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud