Grouping-column-settings of value relations are lost during export of project

[koenigherford]

What is the bug or the crash? What were your expectations and what actually happened?

Grouping-column-settings in value-relations are lost during export of project.
(additionally column-comments are lost).
As a result grouping of value relations is not available in QField any longer.

Seems to be a regression. Did not happen weeks before.

See screenshot

Steps to reproduce the issue

see above

QGIS version

3.42.3-Münster

QFieldSync Version

4.17.3

Operating system name

Windows

Operating system version

Windows 11

Reinstall QFieldSync

• I have a fresh install of the latest QFieldSync version on a new QGIS profile, 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

[suricactus]

Do you know in which qfieldsync version this was working properly?

[koenigherford]

I think, I made a fresh test-export about two weeks before when testing fix of opengisch/QField#6607. Then everything was fine. But I am not fully sure, whether I made a new export or not.

I had a long-term data-collection in the field without intermediate sync to desktop with a project from 27.8.25 which worked - except regrssion #6607 all time. Yesterday I imported the data to desktop-project and created a new offline-project - with observing the issue in the field.

[suricactus]

You used QFieldCloud or used the cable export mechanism?

[koenigherford]

Cable export

[koenigherford]

In the screenshot above I did not recognize that the layername is different between template- and export-project too. I do not know if this may be relevant for you when searching for the reason of the issue.

[nirvn]

@koenigherford , are you offlining the value relation's geometryless layer or copying it?

[koenigherford]

both are configred as "offline-editing"

[nirvn]

@koenigherford , I've not been able to replicate this (in a new try today). If you end up with a small sample project that replicates this situation, let me know!

[github-actions]

The QFieldSync project highly values your report and would love to see it addressed. However, this issue has been left in feedback mode for the last 14 days and is being automatically marked as "stale". If you would like to continue with this issue, please provide any missing information or answer any open questions. If you could resolve the issue yourself meanwhile, please leave a note for future readers with the same problem and close the issue.
In case you should have any uncertainty, please leave a comment and we will be happy to help you proceed with this issue.
If there is no further activity on this issue, it will be closed in a week.

[koenigherford]

The issue is still there today with qfieldsync [4.18.3]. I am using QGIS 3.44.5. currently

I am waiting for an update to 4.0 and the latest 3.44-version by our it-support to make a test with the latestet releases and will answer when available.

[koenigherford]

The issue is still there with qfieldsync 4.18.3 and QGIS 4.0.0. with my project above.

To prepare my project (layers are postgresql-database-layers with "offline-editing"-export-settings in qfieldsync) to a sample-project I tried to manually change the datasource from postgresql-layer to the appropiate layer in data.gpkg of the previously exported offline-project.

I observed, that the layer-name of "hf_u_detailmassn_gesamt" had changed a little bit during prevoius export (usually it seems to be build from former layer-name/data-source with some uuid-extension), but now the part "gesamt" in name is lost.

After changing all the data-sources from postgresql to the local-data.gpkg the export-issue is unfortunately not reproducable any longer.

When changing the datasource form the original postgresql-datasource in my original project to another random postgresql-datasource and back to the original postgresql-datasource the issue is there again.

As I have no idea, how to share the project with reproducable issue I suggest to close the issue for now.

[github-actions]

The QFieldSync project highly values your report and would love to see it addressed. However, this issue has been left in feedback mode for the last 14 days and is being automatically marked as "stale". If you would like to continue with this issue, please provide any missing information or answer any open questions. If you could resolve the issue yourself meanwhile, please leave a note for future readers with the same problem and close the issue.
In case you should have any uncertainty, please leave a comment and we will be happy to help you proceed with this issue.
If there is no further activity on this issue, it will be closed in a week.