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.

Sign up for GitHub

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

Configured form that doesn't exist in REDCAP hanging #41

Open

alexfelmeister opened this issue May 24, 2018 · 1 comment

Assignees

Labels

BRP Tutorial Bugs bug

Collaborator

alexfelmeister commented May 24, 2018 •

edited

Loading

If a configuration contains a form/event combo that does not actually exist in REDCap, system hangs.

Current example: https://brp.research.chop.edu/admin/api/protocoldatasource/211/change/?_changelist_filters=protocol__id__exact%3D81

{
	"unique_event_names": ["demographics_arm_1"],
	"event_labels": ["Demographics"],
	"form_data": {
		"demographics_form": [1],
		"medical_history": [1]
	},
	"record_id_field_name": "record_id",
        "form_order": [
             "0_0",
             "1_0"
        ],
    "labels": [
        1,
        2
     ]

*** Medical History in Chordoma configured but doesn't exist.**
"medical_history": [1]

The text was updated successfully, but these errors were encountered:

alexfelmeister assigned seg1129

alexfelmeister added bug BRP Tutorial Bugs labels

Collaborator Author

alexfelmeister commented May 24, 2018

@seg1129 going through configuration with d3b and finding some items.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment