Dataverse DELETE record operation - #4
Open
matemora wants to merge 3 commits into
Open
Conversation
Author
|
Any comments on this? Will we be able to accept the PR? Really could use those features.... |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This PR adds the ability to delete a Dataverse record by its ID using the existing node structure.
Why this change?
I needed to delete specific records from Dataverse and had to rely on manual HTTP Request nodes, which made the workflow harder to maintain and less intuitive. Adding native support for deletion makes the node more complete and user-friendly.
What was done
Testing
Tested locally using n8n on my machine. Attached screenshots to validate behavior and response handling.
Breaking changes
None. This change is backwards-compatible and does not interfere with current functionality.
Note: I forgot to update the package.json version, sorry!
Let me know if you'd like anything adjusted. Happy to help!