I found the answer in this reply by Shaun.
So, what I understand is this: when I add to APP A a dependency to APP B, if APP B has tables, the IDE creates in APP A a copy of APP B’s tables.
If I want to use the tables of APP B, I need to import that ad explicitly.
That is currently possible only in “Classic IDE” so, if you’re using “Beta IDE” you need to:
-switch to Classic IDE
-go to Tables service
-add Table → choose from available APPs the APP B and the table(s) you need
-switch to Beta IDE.
I think in the future it could be useful one of these two:
- a setting in APP B to state that APP will use only its own tables (to enforce somewhat encapsulation). In this case, using this APP as a dependency won’t trigger
- a flag in APP A, where you set the dependency on APP B, to say “Use dependency’s data tables”. When checked, no APP B’s tables are added to APP A.
BR