Missing relation to all portals of a solution

A customer asked me to replicate his solution into three (he owns 3 very similar companies and he wants to keep all data separated).

Created a new Sybase db
Put it in sybase.config
Created the db connection
Exported the original solution
Disabled the original db connection
Chose CLEAN IMPORT and gave the solution a different name
Chose the new db connection

I did it twice, on my laptop, with no problem.

When I went to the customer, I realized that one of the new solutions needed some data from the old one, so I created an empty db and exported the original solution with sample data. Apart of this, all the steps were the same I described above BUT…
The new solution imported fine, with no errors, but every portal in the solution lost its relation.
The field were there, the data were in the right place, but the portal was linked to no relation.
Reassigning it manually brought it back to work.
Anyway, it’s a very dangerous behaviour (especially if the developer doesn’t get any error, when importing).

I’m not sure I can reproduce it (as I wrote, I did it twice the day before and all went fine). But I think it’s worth of further investigation.

Are you sure the relation used is not in a module?, which is not yet imported at customer site? in all other cases Servoy should give a warning.

Jan Blok:
Are you sure the relation used is not in a module?, which is not yet imported at customer site? in all other cases Servoy should give a warning.

Absolutely sure.
The solution has only one module and it’s my library (no relation in it).
But, as I told you, I performed the same procedure at home, twice. And I didn’t have any problem.

I’m sorry I can’t give you better infos, but I don’t know how to replicate it…

Could it be (I’m only guessing) that some update didn’t complete and the portals informations remained linked to the old name of the solution?