Skip to content

False positive of missing referenced (child) layer - #939

Merged
MarcelGeo merged 2 commits into
masterfrom
fix/find-child-layer
Sep 1, 2026
Merged

False positive of missing referenced (child) layer#939
MarcelGeo merged 2 commits into
masterfrom
fix/find-child-layer

Conversation

@harminius

@harminius harminius commented Aug 31, 2026

Copy link
Copy Markdown
Contributor

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:
image

@MarcelGeo MarcelGeo added this to the 2026.5.2 milestone Sep 1, 2026
@MarcelGeo
MarcelGeo merged commit d66186e into master Sep 1, 2026
8 checks passed
@MarcelGeo
MarcelGeo deleted the fix/find-child-layer branch September 1, 2026 07:29
@MarcelGeo

Copy link
Copy Markdown
Contributor

@IvaKuklica

Copy link
Copy Markdown

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants