Hi Balazs,
This is currently not possible without the use of Context logic, so you will have to resort to code for that. An existing idea can be voted on:
Building that control procedure dynamically using SQL is certainly an option if the situation occurs multiple times in your application and there is a common property between those.
The Context procedure can verify the existence of data in the target table, and if there is no data (yet), then it can disable the Detail tab until there is.
In IAM, we also disable screens if there is no data. The template looks like this:
if not exists (select 1
from oTARGET_TAB] r
where r.model_id = @model_id
and r.branch_id = @branch_id
and r. TARGET_COL] = @=SOURCE_COL]
)
begin
set @tREF]_type = 1;
end;
The Control procedure code will supply the values that the Deploy step will use to replace the parameters inside the brackets. If you want to know more about this, I have written a blog about it here:
You can also use tags to tag the source and/or target table, or tag the reference that should be included in this control procedure:
Hope this helps!