Is there a known limitations with using @cloud_user_name when editing multiple features at once? I am trying to attribute edit multiple features while tracking the latest person to make the edit. @cloud_user_name is returning a null value in this use case. It does work for editing a single feature or adding a new feature.
How do you put the cloud username into a field? And how do you edit multiple features at once? This information might help in replicating your issue.
I am using the variable @cloud_username to auto calculate a field added to the layer.
I attribute edit multiple features at once with the process about 2/3 of the way down this page, section titled ‘Multi-editing of attributes’: Digitize and Edit - Documentarea ecosistemului QField
Hmm, I can confirm this doesn’t work. Must be a bug in QField.
A similar action in a QGIS project does work. Using the Multi-edit mode does populate other fields when a Default value is set for those fields.
I have created a bug report for this:
opened 11:29AM - 12 Dec 25 UTC
### What is the bug or the crash? What were your expectations and what actually … happened?
When editing attributes having multiple features selected, any field with a Default value @cloud_username in the Attributes Form (Apply on update) is not updated.
Using other global variables, such as @qgis_locale, do get updated.
### Steps to reproduce the issue
In a layer with multiple features make sure at least one field is set to have a Default value @cloud_username and tick the checkbox Apply default value on update.
For comparison, also have a field set to have a Default value @qgis_locale and tick the checkbox Apply default value on update.
In QField, select multiple features and edit a field not being the ones with the Default value.
The result is the field with @cloud_username will be NULL and the field wit @qgis_locale will be filled.
### Version
3.7.9
### Operating system name
Android
### Operating system version
16
### Reinstall QField
- [ ] I have a fresh install of the latest QField version, but the problem persists.
- [ ] Problem can be reliably reproduced, doesn't happen randomly.
- [ ] Problem happens with all files and projects, not only some files or projects.
### Additional context
_No response_
Also, when testing I noticed this only applies to @cloud_username and not to standard global variables.