Generate Next Record Name#107
Merged
sburns merged 3 commits intoredcap-tools:masterfrom Dec 18, 2019
Merged
Conversation
Collaborator
|
Is their idea for clients to POST and get a new record ID, use it for the next POST that creates a new record? That's a lot of requests but I'm not running their servers so...shrug? |
Contributor
Author
|
@sburns I think this is only necessary if you have record autonumbering disabled on the REDCap side. We're supporting export to REDCap from another system (https://github.com/RudolfCardinal/camcops) and don't want to make assumptions about how REDCap is configured. Some other bits of the REDCap API are vulnerable to race conditions. |
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
2 participants
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.
I've added support for the Generate Next Record Name API call
