You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Uploading a program exception that overwrites existing program exceptions, and then uploading entity level exceptions returns an error. But uploading entity level exception first and then program exception works.
Steps to reproduce error
Example 1 is where an existing set of program exceptions is overwritten by new program exceptions, followed by attempt to upload entity level exception. This results in an error stating Program exception already exists, but this is not true because there is no program level exception on the field we're trying to make an entity level exception on. However, the field did exist previously as a program level exception before being overwritten by a new program exception, so it suggests there is some caching issue that is not cleared after program exceptions are overwritten.
Example 2 demonstrates scenario where the same exceptions files are used but entity level exceptions are uploaded first, followed by program exceptions. This does not result in any errors.
Example 1: Program has existing program exceptions. A new program exception is uploaded first overwriting the initial program exceptions, and then entity level exception is uploaded. This returns an error.
Initially TEST-INTL has program exceptions which includes a program exception for the percent_tumour_cells_measurement_method = Unknown (done during previous testing). Output from GET endpoint:
There are no entity-level exceptions for TEST-INTL at this point.
Upload new program exceptions file TEST-INTL_program_exceptions.csv which includes only an exception for treatment_setting = Not applicable. This means the initial program exceptions from Step 1 will be overwritten. Output from GET endpoint after program exceptions uploaded:
Can see that program exception for percent_tumour_cells_measurement_method = Unknown is no longer in the list.
Now lets upload an entity-level exception for the "specimen" schema for the percent_tumour_cells_measurement_method = Unknown for 28 donors. First use GET endpoint to confirm that there are no entity-level exceptions for TEST-INTL:
However, there are no program exceptions for percent_tumour_cells_measurement_method (see output from Step 2 above).
Example 2: Upload entity-level exceptions first, then program level exceptions (reverse of Example 1). This will not generate an error.
Start off with same program exceptions we had in Example 1 (Step 1). Upload this program exceptions file: TEST-INTL_program-exceptions_multiple_schema.csv. If you use the GET endpoint after, you will see the same output as Step 1 from Example 1 above.
Upload an entity-level exception for the "specimen" schema for the percent_tumour_cells_measurement_method = Unknown for 28 donors. TEST-INTL_specimen_entity_exceptions.csv. The GET endpoint shows this was successful:
Now upload new program exception for treatment_setting = Not applicable. This will overwrite the program exceptions from Step 1. This does not return an error. The GET endpoint shows the program exception upload is successful:
This means if you upload entity level exceptions first, and then program exceptions after, it will work and the program can have both program and entity level exceptions implemented. But if you upload program exceptions first and then entity level exceptions, an error will result that appears to be related to a caching issue.
Expected Result
Should be able to upload program level exceptions first and then entity level exceptions without generating an error (order of which exceptions uploaded first shouldn't matter).
The text was updated successfully, but these errors were encountered:
Description
Uploading a program exception that overwrites existing program exceptions, and then uploading entity level exceptions returns an error. But uploading entity level exception first and then program exception works.
Steps to reproduce error
Example 1 is where an existing set of program exceptions is overwritten by new program exceptions, followed by attempt to upload entity level exception. This results in an error stating
Program exception already exists
, but this is not true because there is no program level exception on the field we're trying to make an entity level exception on. However, the field did exist previously as a program level exception before being overwritten by a new program exception, so it suggests there is some caching issue that is not cleared after program exceptions are overwritten.Example 2 demonstrates scenario where the same exceptions files are used but entity level exceptions are uploaded first, followed by program exceptions. This does not result in any errors.
Example 1: Program has existing program exceptions. A new program exception is uploaded first overwriting the initial program exceptions, and then entity level exception is uploaded. This returns an error.
TEST-INTL
has program exceptions which includes a program exception for thepercent_tumour_cells_measurement_method
=Unknown
(done during previous testing). Output from GET endpoint:There are no entity-level exceptions for
TEST-INTL
at this point.treatment_setting
=Not applicable
. This means the initial program exceptions from Step 1 will be overwritten. Output from GET endpoint after program exceptions uploaded:Can see that program exception for
percent_tumour_cells_measurement_method
=Unknown
is no longer in the list.percent_tumour_cells_measurement_method
=Unknown
for 28 donors. First use GET endpoint to confirm that there are no entity-level exceptions forTEST-INTL
:Program exception already exists
However, there are no program exceptions for
percent_tumour_cells_measurement_method
(see output from Step 2 above).Example 2: Upload entity-level exceptions first, then program level exceptions (reverse of Example 1). This will not generate an error.
TEST-INTL
using GET endpoint:percent_tumour_cells_measurement_method
=Unknown
for 28 donors. TEST-INTL_specimen_entity_exceptions.csv. The GET endpoint shows this was successful:Entity level exceptions for 28 donors.
treatment_setting
=Not applicable
. This will overwrite the program exceptions from Step 1. This does not return an error. The GET endpoint shows the program exception upload is successful:This means if you upload entity level exceptions first, and then program exceptions after, it will work and the program can have both program and entity level exceptions implemented. But if you upload program exceptions first and then entity level exceptions, an error will result that appears to be related to a caching issue.
Expected Result
Should be able to upload program level exceptions first and then entity level exceptions without generating an error (order of which exceptions uploaded first shouldn't matter).
The text was updated successfully, but these errors were encountered: