Skip to content

Conversation

@alex-cit
Copy link
Contributor

@alex-cit alex-cit commented Nov 20, 2025

  • descriptions
  • relations review
  • variables (renamed, redirects, updated plugin variables)
  • review fixes
  • overview page
  • html and text widgets
  • How to Open a File - using default values is tagged as Advanced but left on the page as it is also included in the public example project
  • How to Link Multiple Records to One Feature edited to match the example project Project forms_one-to-many-relations seems malformed #584

Redirects fail as src/field/photo-sketching/index.md was added to the main in the meantime.
Broken links fail due to 403 wiki.

@alex-cit alex-cit changed the title WIP Forms review Forms review Nov 22, 2025
@alex-cit alex-cit requested a review from tomasMizera November 22, 2025 17:31
Copy link
Contributor

@tomasMizera tomasMizera left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Amazing improvement! Thank you! I suggest we run internal feedback loop now, collect comments from others and then incorporate that with my comments in one go.

{ text: 'How to Use Hyperlinks', link: '/layer/external-link/' },
{ text: 'How to Open a File', link: '/layer/open-file/' },
{ text: 'How to Use Hyperlinks', link: '/layer/external-link/' },
{ text: 'How to Open a Link to a Navigation App', link: '/layer/link-to-navigation/' },
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How about making this shorter? Something like

Suggested change
{ text: 'How to Open a Link to a Navigation App', link: '/layer/link-to-navigation/' },
{ text: 'How to Open a Navigation App', link: '/layer/link-to-navigation/' },

{ text: 'QR Code', link: '/layer/qr-code/' },
{ text: 'Selecting a Single or Multiple Values', link: '/layer/value-select/' },
{ text: 'Selecting Single or Multiple Values', link: '/layer/value-select/' },
{ text: 'Photos', link: '/layer/photos/' },
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we wanted to put photos higher in the list and relations lower


Therefore, **we strongly recommend creating a new field for primary keys and using UUIDs generated by the `uuid()` function when a feature is created [as described below](#generating-unique-ids-uuid)**. UUID (Universally Unique Identifier) ensures that the primary keys are unique even after synchronisation and that the correct features are linked.

## One to many relation setup overview
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How about

Suggested change
## One to many relation setup overview
## Setup overview

1. [Create unique UUID field](#generating-unique-ids-uuid) for your referenced (parent) layer and a field for storing foreign keys in the referencing (child) layer
3. Define the relation in [Project Properties](#setting-up-relation-in-qgis)
4. [Configure Attributes forms](#attributes-forms-configuration-for-1-n-relations) of both layers as needed

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd add a sentence that explains that we are going to talk about these now

Suggested change
Let's walk through each of the points individually now.

Comment on lines +23 to +33
:::tip Example projects available
To see the basic [attachment widget](#photo-attachment-widget-in-qgis) setup for photos, clone <MerginMapsProject id="documentation/form_setup" />.

If you want to [attach multiple photos to one feature](#how-to-attach-multiple-photos-to-one-feature) explore the public project <MerginMapsProject id="documentation/forms_multiple_photos" />.
:::

## Photo attachment widget in QGIS

:::tip Example project available
Clone <MerginMapsProject id="documentation/form_setup" /> to follow this example!
:::
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It feels too much to have two tips for public projects this close. Can we choose only one of them?


![Mergin Maps mobile app relation widget added child feature](./mobile-add-child-feature.webp "Mergin Maps mobile app relation widget added child feature")

## Gallery?
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How about

Suggested change
## Gallery?
## Troubleshooting

instead?

It could also include the common issue "why do I not see my relations in the form?" -> in drag&drop designer you need to manually move the relation into the form.


Selecting values from a drop-down menu is faster than typing them in manually and it also ensures that there are no typos or spelling variations. Additionally, it is possible to create [drill-down (cascade) forms](#drill-down-forms), where a value selected in one field can affect the options available in another field.

|<div style="width:150px"> Widget </div> |Preview in the <MobileAppNameShort />|
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In the future I can imagine some GIFs here to showcase the drill-down functionality 🤔

{ text: 'Photos', link: '/layer/photos/' },
{ text: 'Informational Widgets', link: '/layer/info-widgets/' },
] },
{ text: 'Default Values', link: '/layer/default-values/',
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am bit afraid this rich article will be skipped by people clicking on the arrow icon to expand the menu instead of clicking on the entry. Let's analyse that afterwards.

@tomasMizera tomasMizera merged commit 77c2b61 into forms-refactoring Dec 11, 2025
2 of 4 checks passed
@tomasMizera tomasMizera deleted the forms-review branch December 11, 2025 16:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants