I have the same issue with an 3.5.7 imported solution. The warning applies to a module of the solution.
I also would like to know how to fix this. Although the solution seems to work without problems.
At least for the one you have there is apparently no quick fix. (you are running on 4.1? because 4.1 is a lot better is reporting errors/warnings and offering quick fixes)
You could create a case for it in our support system and attach your workspace, so our engineers can have a look if this specific case can have a quick fix in future versions.
Or you can analyse the issue yourself, by digging into the file structure and content of the workspace
pbakker:
At least for the one you have there is apparently no quick fix. (you are running on 4.1? because 4.1 is a lot better is reporting errors/warnings and offering quick fixes)
Yes this is 4.1 final.
I will see what I can find myself or else send the workspace to support.
Hi,
I’m also getting this error & unsure what to do.
It occurred for some rectangle objects I had placed in a portal on a form, but had not named.
But, I am also getting a lot for table calcs. with this extra comment ‘Entity <calc_name> has been manually moved?’! (Calcs all seem to be fine in 3.5.7)
What does that mean?
Does a right-click on the warning/error offer a quick fix?
You can have a look if you see something suspicious in the actual file containing the calcs.
Otherwise you can create a case in our support system and attach a copy of your zipped workspace.
The issue that non named rectangles in a portal cause errors/warnings about a broken file structure seems wrong to me. Can you create a case for this as well and attach the zipped workspace?
pbakker:
Does a right-click on the warning/error offer a quick fix?
No, it didn’t, but see below…
pbakker:
You can have a look if you see something suspicious in the actual file containing the calcs.
Otherwise you can create a case in our support system and attach a copy of your zipped workspace.
Firstly, before I solved things below, it seemed as if for one table, ‘line_items’, ALL calculations AND aggregations were not there, so I dug around in the Workspace and the actual files.
Then, I think I worked it out!
The original solution was based on the sample ‘crm’ that came with Servoy 2. There seemed to be some weird casing issue with some of the tables, so at some point (I think) the table ‘line_items’ was called ‘LINE_ITEMS’ (not sure how, as I thought Sybase only allowed lower case table names…).
Anyway, I quit Servoy 4.1, renamed the ‘LINE_ITEMS.obj’ file to ‘line_items.obj’ and changed the tableName:“LINE_ITEMS” to tableName:“line_items”, saved it and relaunched Servoy. Once it had started, after a few seconds, loads of the errors disappeared including almost all of the ‘Structure … broken’ errors, except the rectangle ones!
Maybe the solution importer/parser should automatically lowercase all table names & objects to stop this kind of thing happening again (unless some SQL dbs allow UPPER CASE table names?)
pbakker:
The issue that non named rectangles in a portal cause errors/warnings about a broken file structure seems wrong to me. Can you create a case for this as well and attach the zipped workspace?
Paul
If I get a chance. I was doing this on my clients time.
Do I need to just zip up the workspace folder for this particular solution, or the whole thing (with all my other clients solutions)?
I too have a couple of warning saying the structure is broken. How were you able to determine the source of the one issue? One of the warnings points to a calc, but the other doesn’t point to anything. Not sure where to look to investigate.
cyarbrough:
I too have a couple of warning saying the structure is broken. How were you able to determine the source of the one issue? One of the warnings points to a calc, but the other doesn’t point to anything. Not sure where to look to investigate.
Some of my errors related to aggregates, so I looked at that table & there weren’t any, so then I checked the calcs., which also had errors, and they weren’t there!
So I then looked in my ‘workspace’ folder (on Mac), in solution_name folder, then the ‘datasources’ folder which is where it seems to store all calcs & aggs., and they were there, even though deve. wasn’t showing them!
Then I spotted the case issues, where most table names were in lower case, but that file was in UPPER, along with its ‘.obj’ file, which in the text content of it also had the table name in UPPER case, so I just edited the names and contents, re-launched Servoy & it all worked.
Can’t be sure that is your problem, but at least do have a look in the workspace folder/directory for the correct files.
Everything seems to be text files now for 4.1, so it should be easy.
tgs:
I have migrated my solution dev. in Servoy 3.5.7 to 4.1. I got a lot of error warnings in ‘Problems’, but I could fix all besides one:
Structure of the files for solution MySolution is broken (incorrect parent-child combination).
Does anybody know how I can fix that warning issue?
Thomas
This errormessage also occurs when you whave a solution A that uses module B and module B references module C
But module C references also module B again
3.5.x accepted that, 4.1 gives the above message.
Is that your case? In that case you probably should merge modules B and C into 1 module (I have to do that myself also )
So try to make a treeview with modules calling other modules and see if your tree is repeating itself.
This errormessage also occurs when you whave a solution A that uses module B and module B references module C
But module C references also module B again
Martin, this is not actually true.
This message occurs only when an element is on an unexpected place in the hierarchy (for instance a form as child of a form in stead of a solution)
It occurred for some rectangle objects I had placed in a portal on a form, but had not named.
This is a wrong warning, Servoy gives a warning about shapes as child of a portal but that is allowed, this will be corrected in next release.
Anyway, I quit Servoy 4.1, renamed the ‘LINE_ITEMS.obj’ file to ‘line_items.obj’ and changed the tableName:“LINE_ITEMS” to tableName:“line_items”, saved it and relaunched Servoy. Once it had started, after a few seconds, loads of the errors disappeared
That is the correct fix.
Note that servoy should store table names always in lowercase in the file system, regardless of the casing in the actual database table name.
It is very strange that the file and directory were created with uppercase name.
Rafi, please create a case with the .servoy file attached so we can fix this.
This errormessage also occurs when you whave a solution A that uses module B and module B references module C
But module C references also module B again
Martin, this is not actually true.
This message occurs only when an element is on an unexpected place in the hierarchy (for instance a form as child of a form in stead of a solution)
Rob
Rob,
I do have the same error in 4.1, because of the circular reference.
I posted this earlier in the forum and Paul told me that I had to merge B and C into 1 module because the situation where module B uses module C and module C uses module B, gives the message.
Do I understand that this is incorrect and that you think that this warning has another reason?