Hi Laura, Is it an idea to create an issue for it at: https://github.com/qgis/QGIS/issues (you will need a github account).
Because then you are 'forced' to give some more information then you provide here :-) Like: what version of QGIS are you using on what platform, and can you describe the process on how others should see this issue too (to reproduce this behaviour). For example: are we creating new features here? This way interested people can either: - confirm the issue (and then it is up to developers to fix it) - or could find out why it is not working for you (and hopefully it is then working again). If you are not willing/able to create an issue, then please provide the information here (QGIS-version and a clear set of steps to reproduce). Regards, Richard Duivenvoorde On 1/14/26 21:02, Laura via QGIS-User wrote:
Hi everyone, I think my last email may not have arrived in a readable format (it was HTML), so here it is again: Is anyone else experiencing the issue that default values can no longer be set? For example, when I set a function as a default value (e.g. for the UUID) it is saved correctly at first. But when I reopen the attribute form, the default value field shows the previous preview (e.g. 123456) value instead. So no new UUID is generated. I have the same problem even if I don’t set the command as a default value and only select the UUID generator as the widget type. I experience this Problem with every default value i set. Kind regards Laura _______________________________________________ QGIS-User mailing list [email protected] List info: https://lists.osgeo.org/mailman/listinfo/qgis-user Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
_______________________________________________ QGIS-User mailing list [email protected] List info: https://lists.osgeo.org/mailman/listinfo/qgis-user Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
