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
It adds input_id as a prefix. This should be unique inside the call (i.e. repetitions are not allowed). This however isn't true for a dataname. What if you need to do merge of multiple selectors from the same dataset?
SELECTOR1:
id: id1
ADAE
select: X, Y, Z
filter: COL_1 = VAL_1
key: X, Y
SELECTOR2:
id: id2
ADAE
select: X, Y, Z
filter: COL_1 = VAL_2
key: X, Y
It adds input_id as a prefix. This should be unique inside the call (i.e. repetitions are not allowed). This however isn't true for a dataname. What if you need to do merge of multiple selectors from the same dataset?
SELECTOR1:
id: id1
ADAE
select: X, Y, Z
filter: COL_1 = VAL_1
key: X, Y
SELECTOR2:
id: id2
ADAE
select: X, Y, Z
filter: COL_1 = VAL_2
key: X, Y
Provenance:
Creator: pawelru
It does, but it doesn't add the same input_id to the same data_extract_spec if the order of input is scrambled. And it probably should, right?
to reproduce:
Notice that
ASTDY
andAENDY
are columns that are passed in from bothADAE
andADCM
Inside of
srv_g_patient_timeline
:If you press the Show R code button on the app:
data_merge_module
tries to resolve this conflict by renaming. However, the renaming is unpredictable.If instead, the developer rearranges the order:
Pressing SRC:
Solution:
ASTDY -> ADAE.ASTDY
AENDY -> ADAE.AENDY
ASTDY -> ADCM.ASTDY
AENDY -> ADCM.AENDY
This actually makes more sense, too.
Provenance:
The text was updated successfully, but these errors were encountered: