When attempting to import an update of a solution remotely I keep getting the following error:
“com.servoy.j2db.persistence.RepositoryException: There is already a solution with the name Choices”.
I have previously done the same kind of remote import for another customer without any problems. Also, I can import the solution back into my own local test installation with no trouble.
Servoy Version R2 2.1.2-build 315
Java version 1.4.2_04-b05 (Windows)
This means that the server contains a solution with the same name but a different global identifier used for importing and exporting.
This can happen when a repository database is copied to duplicate a solution before it has ever been exported, in which case exports from the different repositories will cause the same solution to have different global identifiers and therefore will be seen as being different.
This can also happen when you at some point do an “Import As” instead of a normal import.
The only solution at this point is to export your solution from the server for backup purposes, delete it, and then do a clean import from your .servoy file.
sebster:
This means that the server contains a solution with the same name but a different global identifier used for importing and exporting.
I would like to know more about the “global identifier” and how it works. Knowing more about it might help me to avoid similar problems in the future. It sounds like having the ability to reassign a global indentifier might be a nice feature request, or is it already possible to somehow create a global identifier that would match a prior global identifier? Perhaps the global identifier is just an incremented id that can not be set back to an earlier lower numbered id. If so, how are these global identifier numbers issued and maintained by Servoy?