* That's why this test has 2 versions that reflect both scenarios. We'll call them "normal" and "workaround".
* Until the underlying issue is fixed, "normal" scenario will be skipped.
*
* Related issues: metabase#10474, metabase#14629
*/
cy.request("POST","/api/card",{
name:"EE_520_Q1",
dataset_query:{
database:1,
native:{
query:
"SELECT * FROM ORDERS WHERE USER_ID={{sandbox}} AND TOTAL>10",
"template-tags":{
sandbox:{
"display-name":"Sandbox",
id:"1115dc4f-6b9d-812e-7f72-b87ab885c88a",
name:"sandbox",
type:"number",
["normal","workaround"].forEach(test=>{
it(`${test.toUpperCase()} version:\n advanced sandboxing should not ignore data model features like object detail of FK (metabase-enterprise#520)`,()=>{
// Remove of comment-out to enable test run for both scenarios