What could this error mean?
I have complex multi-level relationships, as well as many-to-many relationships. I am deliberately not specifying all the relationships here so as not to confuse you. I just want to know - is this error a bug? Is it related to incorrectly build (or overly complex) relationships that I am trying to display in the frontend?
Is there a solution to this problem? I have now built a fairly complex structure, but this error now prevents me from correcting the current design, as the existing records are not loading.
Is there any way to disable the effect of the error on data display? After all, the presence of records in List mode allows you to make settings. Now there is a problem, and I will have to delete my current block and reconfigure it… It took me about 5 hours to configure it, and now I will have to delete everything. That’s bad… (((
I just recreated a multi-level “query” of the 1st level value on a separate page of a record in the 4th level inheritance chain, and everything was configured correctly, with no errors.
I can assume (but I may be wrong) that the error occurs due to long field names and at some point in a complex query there is not enough character space. Could this be the case? In the screenshot above in the error message, you can see that the phrase is cut off (part of the word “…-> carg” is displayed). Could this be one of the reasons? Or is the error not related to this hypothesis?
The screenshot below shows a similar multi-level structure, but when you try to enable the Order (“Заказ” - rus.) field in the settings, an error immediately appears.
Hello, please provide a reproduction of the issue in the demo environment.
https://a_8hwne7u84ho.v13.demo.nocobase.com/admin/
(NocoBase default username and password)
I recreated my working collection scheme on your test platform and got a similar error
There are quite complex relationships there, and I can also assume that this error occurs due to duplicate inheritance through a direct connection (i.e., the exact same connection can be obtained through a “long chain” of relationships).
In short, the logic is as follows (for general understanding): there is a structure (the structure list shows a one-to-many top-down hierarchy)
- Orders
-
-
-
-
-
- Contractor Transportation
-
-
-
- Contractor Transportation Routes
In addition, it should be noted that there is a many-to-many relationship between Orders and Contractor Bids, and between Transportation and Contractor Transportation - there is a one-to-many relationship, and between Routes in Transportation and Contractor Transportation Routes - there is a one-to-many relationship. (Perhaps these additional relationships are what “break” the existing structure, but I am not sure about that…).
Below is a video file where I showed how the error appears (as a result of going to each internal page detailing each subordinate record): as a result of attempting to display the parent record field of the Order at the very last “level” - in the list of Contractor Transportation Routes.

Please watch the video until the end (the error is shown at the end). The platform slows down a little there, so it seems like the video is “freezing,” but you need to wait.
Perhaps in my particular case, the data structure is very complex and has “intersections” in the connections, but such relationships are still visible in the frontend. In other words, the platform visually allows you to display very deep relationships across several related collections, so it is logical that this functionality should work correctly and logically.
NocoBase is a very cool platform that uses a very powerful and functional visual query builder in the frontend. I have studied many no-code builders, but NocoBase is the best one in my opinion, so I really want its functionality to be at the top level among all no-code platforms!
@hongboji, this error literally follows me everywhere…)) It shows up on the Classic Page version 1 (on the Modern Page version 2 with similar settings, the error does not occur, but the value I want to display does not appear either).
I can assume that it is related to the use of the Many-to-Many field type. Probably, some kind of “cyclicity” is performed in the queries, which is why the error “table name specified more than once” occurs. Although everything is configured logically, the relationships should work correctly… I am not an expert in this, but I am sure that you will professionally figure out what the problem is!
I’m sorry, I’ve watched this GIF more than 5 times and tried to reproduce the page steps you provided many times, but I still can’t find the problem. The animation can’t be paused, and you haven’t provided the final URL of the error, making it very difficult for me to solve this problem.
I made a video for you where you can pause the frames.
Below is a direct link to the page where the error occurs.
https://a_8hwne7u84ho.v13.demo.nocobase.com/admin/e4ynir9prxw/popups/w1chkjsbmq0/filterbytk/338414241251328/tab/gbcjq33l26d/ popups/i0ed4989dwx/filterbytk/340969411903488/sourceid/338414241251328/tab/d9qw609ekkt/ popups/11ma552tf1x/filterbytk/340969762127872/sourceid/340969411903488/tab/3ird5jrrv2u
I prepared a block where the field needs to be displayed, but an error appears. In the screenshot, I showed how to reproduce the error (you just need to turn on switcher of the field Orders Test using the existing relationships, as shown in the screenshot. If the error does not appear immediately, simply reload the page and it will appear. Or, without reloading, first click the switch back, then reload the page, and then turn the field back on again - the error should appear instantly.).
Please take a look at this error. If anything is unclear, let me know. It is very important for me to fix it, because I don’t understand why it occurs, since everything is allowed in the settings and I logically build relationships between collections.
I am 99.9% sure that the error is related to the many-to-many relationship in this chain of relationships…