Servoy 7.3

Classic Servoy
41

Yes, admin page. You don’t have to delete or restart.
Just export/import when it’s ready for deployment.

42

Ok, thanks!

43

Andrei Costescu:
Yes, admin page. You don’t have to delete or restart.

Perhaps I’m doing something wrong… I’ve create a solution, exported and then imported in server. Ok. Then, I’ve changed something in the solution and exported again. But when I’ve tried to imported to server I’ve receive this error: “Solution ‘MySolution’ already exists. Import failed.”

44

Don’t check “Clean import”. You probably checked that and specified as “New name” the same solution name. That option is useful if you want to import as a different solution name - with release version 1. Just do a normal import that will put a new release version of your solution on the app. server and activate that release.

45

I don’t chek “clean import”.

I tried to import checking and unchecking “Activate new release of imported solution and modules”. Also, I exported the solution without its modules. Unsuccessfully :cry:

46

Is your repository still set to a code repository server? I suspect you can’t import via the admin pages if this is the case.

47

It’s a fresh install, I think, but I’m going to create a new repository and I0ll try again.

48

I just tried a fresh install of 7.3 - with sample solutions.
Started developer - imported and modified something in servoy_sample_crm solution, exported it - then closed developer, started application server, checked that the solution loaded in web-client, imported the new version from admin paged (just selected the .servoy file and imported, without changing anything else) successfully, then started another browser session and the solution that loaded was the new one.

Tried a similar thing with smart client and it worked as expected.

If you still have problems after checking what David suggested, please make a separate topic to sort this out and put a link to it here - as this doesn’t seem necessarily related to 7.3 release and the discussion is getting long.

49

Hi, I’ve made a fresh install and it worked fine.

Also, I’ve been playing around SVN and it’s very interesting!!

Thanks to all!

50

You are welcome! :)

51

With SVN, do you still have to define a “repository_server” database in developer?

52

Not in developer.

53

Hi

We are productive with 7.3, now. But there are still open problems, I’d like to come back to (see earlier post):

  1. I have entered a case in the support system with an example solution. The error still occurs and is reproducible. Even if I get a lot of feedback how to optimize the code (which I cannot so far), I’m sure it should NOT raise an error.

  2. Still unsolved. Any ideas?

  3. (new): In an application which uses tow databases, we get the following entry in the console:

ERROR - Debug                      - Relation invoices_origin_for_invoices cannot be used in a find (multi server)

I do not use a find. The application runs fine, but the error makes us unsure. One form uses a table in one database, the other form displays data of a table in an other database, retrieved with a Servoy relation.

Help is very appreciated.
Regards
Birgit

54
  1. Ok. I guess that will continue as a case then. (post case number here as well for reference if you think it can help others in the future)
  2. Do you use odd/even/selected styling? Does it work if you don’t use a type-ahead in it? Do all columns in all records have that blue background or just the type-ahead’s column?
  3. That error message only appears if you have a “find mode” record. So if you see that in the log, one foundset is in find mode at that time and a relation based on that find record is accessed. If you are sure you (or the user) didn’t put such a foundset in find mode at the time and you can create a sample solution for it then you should create a case.