It would be great to have possibilty to move relations from one solution to another one
Now I have to create new solution and prefix the relation name with NEW
Remove the old relation
And rename the NEW relation to the correct relationname (srctable_to_desttable)
By the way, I have to move about > 50 relations , because I’m splitting my modules (1 module with all forms and 1 module with all relations, calculations, global methods)
I added also a request (# 239369)
YES!! you have my vote also.
You can allready do this in servoy.
If you open the view Project Explorer and select your relations right-click and choose move.
Thanks Sanneke,
I didn’t know that. I didn’t want to move it directly on OS-level in the workspace because Servoy probably needs to change the UUID
Maybe a good idea to make this also possible in the solution explorer ?
Hi Martin,
I just saw that in Tano that is implemented in the solution explorer.
OK, then request # 239369 can be set to “Done”
What I was afraid of, did happen.
My solution doesn’t import on my application server
So be careful when moving relations in Project Explorer mode
[error] com.servoy.j2db.persistence.RepositoryException: Root object of element _to_sales_invoice has changed (object has been moved), from globis_sales to globis_sales_methods; delete solution globis_sales first or clean import.
sanneke:
Hi Martin,I just saw that in Tano that is implemented in the solution explorer.
Sanneke, is this also the case for calculations, aggregations, table events, etc?
I tried the same as Martin, but doing it via the project explorer, generates all kind of errors in the end…
Harjo:
sanneke:
Hi Martin,I just saw that in Tano that is implemented in the solution explorer.
Sanneke, is this also the case for calculations, aggregations, table events, etc?
I tried the same as Martin, but doing it via the project explorer, generates all kind of errors in the end…
It’s implemented for forms,relations,valuelists,media (move and duplicate) - in Tano.
martinh:
What I was afraid of, did happen.My solution doesn’t import on my application server
So be careful when moving relations in Project Explorer mode
[error] com.servoy.j2db.persistence.RepositoryException: Root object of element _to_sales_invoice has changed (object has been moved), from globis_sales to globis_sales_methods; delete solution globis_sales first or clean import.
Please open a case with this scenario.
lvostinar:
Harjo:
It’s implemented for forms,relations,valuelists,media (move and duplicate) - in Tano.
so not for calcs, table events, aggregates?
I have created allready a case for this, a while ago: case: 233,423
I am sorry I forgot about the error with importing. I created a case about it, because it is the same in Tano.
I only use this solution for moving relations, so I don’t know about calculations, aggregations, table events, etc, but the fact that you get errors says enough.
Harjo:
lvostinar:
Harjo:
It’s implemented for forms,relations,valuelists,media (move and duplicate) - in Tano.so not for calcs, table events, aggregates?
I agree that for calcs, table events, aggregates this should also be available
Even global methods and variables should be moved to another module in an easy way.
Now copy the method; remove the UUID header and paste it in another method, so that it gets a new UUID
Because moving a method including the UUID-header is giving troubles on import solution where deploying the solution
Harjo:
lvostinar:
Harjo:
It’s implemented for forms,relations,valuelists,media (move and duplicate) - in Tano.so not for calcs, table events, aggregates?
I have created allready a case for this, a while ago: case: 233,423
I’m afraid not, the case is not started yet.
oke, I changed this case a bit, so that it includes global methods & variables also…
move table events? How do you want to do that?
Table event by itself is a global method.
The configuration is a certain file yes but that is prety much hidden (thats just the table editor) so what do you want to select to be moved? The complete table node for that solution? But that is way more then just table events.
What we should look at is that a uuid should be able to move around… That shouldnt be a problem as long as it is not a duplicate.
Johan,
you are right, table events are allready global, my mistake…
what I mean was calculations & aggregations, (solution/module based things) so we can split up (older) Servoy solution much easier into modules.
We fixed the problem with move at import. Now, when moving an element it will actually create an element with different uuid and update all references (because the repository does not support having the same element with two different parents).
OK perfect. Will it be in 4.1.5?
martinh:
OK perfect. Will it be in 4.1.5?
Sorry, forgot to mention, the fix is for 5.0 (so 5.0 b3 ).
Harjo:
Johan,you are right, table events are allready global, my mistake…
what I mean was calculations & aggregations, (solution/module based things) so we can split up (older) Servoy solution much easier into modules.
This will be done in Servoy 6.1 . (calculations & aggregations move/duplicate)