Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

JSON file tracking which records are removed from data packages #5

Open
abvogel opened this issue Jun 14, 2019 · 3 comments
Open

JSON file tracking which records are removed from data packages #5

abvogel opened this issue Jun 14, 2019 · 3 comments
Labels
enhancement New feature or request

Comments

@abvogel
Copy link
Owner

abvogel commented Jun 14, 2019

No description provided.

@abvogel abvogel added the enhancement New feature or request label Jun 14, 2019
@rnwood
Copy link

rnwood commented Mar 11, 2024

Hi. Thanks for this tool.

What's your recommendation on how to handle removing (or perhaps deactivating) records that are in the target instance but not (or no longer) in the source data?

I figure this feature is related to that, so how are you currently handling this?

@abvogel
Copy link
Owner Author

abvogel commented Mar 11, 2024

@rnwood - Ideally, you could mark them as inactive, and if filters are set up properly they'd drop out of views/plugins/whatever. Otherwise, I've seen manual steps, or PowerShell scripts to identify/remove specific records, or C# code in the Package Deployer. There isn't a "mirror" capability currently, as the Config Migration Tool also doesn't handle deletes.

@rnwood
Copy link

rnwood commented Mar 12, 2024

@abvogel thanks for the confirmation.

So a nice idea for a tool here to complement the CMT and your tool would be something that can remove/deactivate the records identified by a data package.

Then you could run an export after applying the main package and a "subtract" with your tool would create the package identifying the extraneous records to be fed in for deletion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants