Yes, this is always tricky with Servoy! In older version of Servoy this was really never a problem, because you had to create form, for working with records.
In new versions of Servoy, we more & more, use on the fly foundsets in code, and these tables will not be referenced by Servoy.
So we always create a dummy form, for every table, we use in a solution, to prevent this…
on exporting the solution there’s also a checkbox to make Servoy export every table from the referenced servers.
Look closely, that is says: referenced, so if you use a server, which you only use in code, and never referenced in form or relation, this also will break…
I also thougt of that, but that only works for tables not for views
The only workaround is to create dummy usage ( like a relation ) and the servoy will export it.
I tested and it also imports on servoy server, so my issue is solved.
I am also looking into to creating a primary key on the view, that is possible in Oracle.