What version of EMX2 are you using (see footer)
Software version: v10.58.0

Describe the bug
I encountered an issue while attempting to save information for multiple treatments associated with a subject in EMX2. Here's the scenario:

1. I have a subject in the database.
2. There are multiple questions regarding treatment for different conditions, such as epilepsy and delayed puberty.
3. I used an "extend" to specify treatment, with each question linking back to the "extendTreatment" entity.
4. When attempting to save information for more than one treatment for a patient, I encountered the following error:
5. failed.: Transaction failed: SQL [update "extendTreatment"."rasopathies" set "belongsToSubject" = 'test', "subTypeRasopathy" = 'schwannomatosis', "prenatalImaging" = 'na', "abnormalThyroid" = 'hyper', "abnormalThyroidTreatment" = cast('{"d994a6d1-aa3a-493c-8f11-3f0c23b337d1"}' as varchar[]), "diabetes" = 'yes', "diabetesTreatment" = cast('{"b9675a4e-9c7c-4e93-8bf1-d6021bdc2312"}' as varchar[]), "linkToAuxology" = cast('{"b059f962-84df-417a-a5f1-8f2d2566714a"}' as varchar[]), "delayedPuberty" = 'yes', "delayedPubertyTreatment" = cast('{"97d49ca1-debe-4e45-a932-a25b3f13cf19"}' as varchar[]), "intellectualDisability" = 'na', "abnormalHeartMorphology" = 'no', "cardiomyopathy" = cast('{"no"}' as varchar[]), "lymphaticAnomaly" = 'no', "deafnessHearingImpairment" = 'no', "label" = 'schwannomatosis', "mg_draft" = false, "mg_updatedBy" = 'admin', "mg_updatedOn" = timestamp '2024-04-26 11:28:55.939786961' where "id" = '6ebb5c1f-4280-48b2-84b4-e11fea8f6a24']; Batch entry 0 update "extendTreatment"."rasopathies" set "belongsToSubject" = 'test', "subTypeRasopathy" = 'schwannomatosis', "prenatalImaging" = 'na', "abnormalThyroid" = 'hyper', "abnormalThyroidTreatment" = cast('{"d994a6d1-aa3a-493c-8f11-3f0c23b337d1"}' as varchar[]), "diabetes" = 'yes', "diabetesTreatment" = cast('{"b9675a4e-9c7c-4e93-8bf1-d6021bdc2312"}' as varchar[]), "linkToAuxology" = cast('{"b059f962-84df-417a-a5f1-8f2d2566714a"}' as varchar[]), "delayedPuberty" = 'yes', "delayedPubertyTreatment" = cast('{"97d49ca1-debe-4e45-a932-a25b3f13cf19"}' as varchar[]), "intellectualDisability" = 'na', "abnormalHeartMorphology" = 'no', "cardiomyopathy" = cast('{"no"}' as varchar[]), "lymphaticAnomaly" = 'no', "deafnessHearingImpairment" = 'no', "label" = 'schwannomatosis', "mg_draft" = false, "mg_updatedBy" = 'admin', "mg_updatedOn" = timestamp '2024-04-26 11:28:55.939786961' where "id" = '6ebb5c1f-4280-48b2-84b4-e11fea8f6a24' was aborted: ERROR: column "belongsToRASopathy" of relation "treatmentabnormalThyroid" does not exist Where: PL/pgSQL function "extendTreatment"."1rasopathies-abnormalThyroidTreatment_UPDATE"() line 16 at SQL statement Call getNextException to see other errors in the batch..
   This error prevents me from saving data for multiple treatments for the same subject. It seems that there's a limitation or inconsistency in the database schema or data linkage that is causing this issue. Added treatments are visible in treatment tables.

To Reproduce
Steps to reproduce the behavior:

1. Create test database
2. Upload datamodel with additional ontologies (and dataprovider (optional))
3. Go to "/tables/#/Rasopathies"
4. Create dummy patient info (fill in all mandatory fields)
5. add two treatments, go to 'growth &GH', add 'yes' in question Abnormal thyroid function.
6. add 'treatmentabnormalThyroidFunction'
7. add 'yes' in question 'Diabetes'
8. add 'treatmentDiabetes'
9. See error

Expected behavior
I should be able to save information for multiple treatments associated with a subject without encountering any errors. The database schema and data linkage should support this functionality seamlessly.

Screenshots

ontology1714124552335.zip

dashboard_data.zip
extendTreatment1714125348515.zip