In my solution there is a module that is completely designed by my customer. Let’s call that module “customer”. The main idea is that customer’s can modify some aspects of the solution (basically which fields to display). So far, so good. Now I want to put my own module “customer” in place of that to have a starting point for other installations.
I thought I simply delete their module and create a new one with the same name. Then I figured, that the forms I want to use don’t show up in my solution, although the module has the same name and so do the forms.
My question is: how does Servoy reference a form inside a module (obviously not only by name)? And what is best practice for a situation like that? It seems that the only way to do that is to take the current “customer” module and delete their stuff.
patrick:
My question is: how does Servoy reference a form inside a module (obviously not only by name)? And what is best practice for a situation like that?.
I may have experienced a similar situation with importing a solution update. Prior to the import I renamed a form with the intent of not having the form overwritten by the import. However, the form was overwritten anyway, suggesting that the form id was used during the import and not the form name.
Servoy tracks the OBJECTS themselves, not their names. Thus renames of solutions or forms are nog going to help. The proper way to do this for solutions is to do an “import as”, after which the new solution will be a proper duplicate of the other solution, and revision tracking will no longer work for the new solution… It’s like making an entirely new and unrelated copy. For forms it’s pretty much the same story, use the “duplicate form” functionality if you want make a copy of a form with a different name.