Hi @SDF1,
Thanks a lot for your response !
I tried this option by switching the table which is "on top" (I have seen it in another topic in the forum), it does enable to enter other covariates from another table, but I don't have all possible combinations that are done between the "big" table A and the "small" table B, so it ends up with a poorly efficient design, and covariates row number is not higher than the number of rows from the small table, which is an indication that not all combinations have been done.
Moreover, doing it this way does create a correlation/link between covariates from table A and covariates from table B (JMP seems to join the covariates in the design creation by row number), which is not the situation I have experimentally, as covariates A are independent from covariates B.
I have found a workaround to prepare the covariates datatable (with all combinations, so nA x nB rows) quickly with another low-code tool, but it would be great if there was a solution where JMP would be able to store the data in memory and do the combinations in the background when building the design based on two covariates tables.
Thanks a lot for the interest and this option !
Victor GUILLER
L'Oréal Data & Analytics
"It is not unusual for a well-designed experiment to analyze itself" (Box, Hunter and Hunter)