False positive of missing referenced (child) layer - #939
Merged
Conversation
MarcelGeo
approved these changes
Sep 1, 2026
Contributor
Testing note:Test passed ✅. Reproduced the reported false-positive "Referenced table is missing from the project" warning using a layer field with a Value Relation widget pointing to another layer — the referenced layer was removed from the project and re-added from the same source, causing the widget's layer reference to break and trigger the warning even though the layer was present under the same name/source. Retested the exact same steps on the updated plugin build with the fix applied — the warning no longer appears. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes https://odoo.lutraconsulting.co.uk/odoo/my-tickets/16926
Issue:
When a child layer was removed from the project and then re-added, a new layer ID is generated. This new ID does not match the one stored in the field config of the reference (parent) layer.
Adding new features with the relation works fine, as QGS has a special method for this which falls back to the layer name and its source when it fails to find a matching layer ID.
Let's follow the standard method, which was introduced in version 3.2.
original warning:
