Skip to content

Fix handling of current_parent* driven default value expression when editing a child feature#7682

Open
nirvn wants to merge 1 commit into
masterfrom
child_editing_current_parent_fix
Open

Fix handling of current_parent* driven default value expression when editing a child feature#7682
nirvn wants to merge 1 commit into
masterfrom
child_editing_current_parent_fix

Conversation

@nirvn

@nirvn nirvn commented Jul 4, 2026

Copy link
Copy Markdown
Member

This PR fixes #7668

Looking into the issue revealed a couple of issues this PR addresses:

  • we had a poorly designed method to check for the usage of a parent feature driving default value expressions; and
  • we did not refresh parent feature driven default value expressions when opening a child feature in editing mode.

I've also taken the time to deduplicate code here to ease maintenance and improvements to child editing.

@qfield-fairy

qfield-fairy commented Jul 4, 2026

Copy link
Copy Markdown
Collaborator

🍎 MacOS DMG universal builds

Download a MacOS DMG universal build of this PR for testing.
(Built from commit 0a4dacd)

📱 Android builds

Download an Android arm64 build of this PR for testing.
(Built from commit 0a4dacd)

Other Android architectures

🪟 Windows builds

Download a Windows build of this PR for testing and for arm64.

(Built from commit 0a4dacd)

🐧 Linux AppImage builds

Download a Linux AppImage build of this PR for testing.
(Built from commit 0a4dacd)

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.

No automatic update in child field with reference value depending on parent field value

2 participants