Structure of the files for solution is broken

Classic Servoy
1

Hi,

I’m testing the migration from 3.5 to 4.1.1

I have imported my solution in 4.1.1

In one of my solutions I get the following message:

Structure of the files for solution mySolution is broken (incorrect parent-child combination).

What can this be? Where do I have to look to find the reason for this error?

Martin

2

Using Team synchronization, in 4.1 and now in 4.1.1, I’m also having this strange warning. Seems to be located in the global.js file.
I’m a bit worried about the word broken…

3

As far as I can see it looks like an element that is in the repository, but not accessible in designer.
When I removed the xxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.obj file in the workspace then error is gone

4

This warning is related to files in the workspace; it means that a certain element has a different parent type than it would be expected . This probably happens when doing manual operations to workspace files. The file has to be deleted/moved manually.

5

I noticed indeed when removing this file from workspace, that the error disappears.
But I didn’t make any manual changes in the workspace because the solution was imported from a 3.5 solution and then checked out
So the origin is probably in 3.5

Do I need to remove this also in the 3.5 repository, or isn’t it that important that it can stay in the 3.5. repository without problems?

6

martinh:
I noticed indeed when removing this file from workspace, that the error disappears.
But I didn’t make any manual changes in the workspace because the solution was imported from a 3.5 solution and then checked out
So the origin is probably in 3.5

Do I need to remove this also in the 3.5 repository, or isn’t it that important that it can stay in the 3.5. repository without problems?

Difficult to say what happens without further information, what element is the error about ? Can you identify the parent-child problem ? (from marker path)

7

It is a form on a tabpanel
But it doesn’t give any error in 3.5
So it looks like it thinks that a form is on a tabpanel, but in fact it isn’t
And also when I remove this obj file in the workspace in 4.1, then all seems to work
So it looks like some old data in the repository

If removing this file in workspace is enough to avoid this message and all works OK (it looks like that), then it is OK for me

8

Martin,

If you can attach the 3.5 solution file to a case maybe we can reproduce this error, is that possible?

Rob

9

Rob,

Case 202448 was created with the solution and the UUID of the object that causes the problem

Martin