Postgres connection doesn’t work, it creates a .gpkg instead

I have points and tracks stored in a PostgreSQL database that I want to access from QField. When I set the layer to “Directly access data source” in QGIS, it still creates a .gpkg layer containing the current geometries.

Is there a way to have QField access my PostgreSQL server directly instead?

HI @ZahnKurt
It sounds like you are choosing the first option when converting your project into a cloud project. Try to use the SECOND option when creating your cloud project - read the details under each option and you will find that it indicates to use the second option, when working with Postgres :slight_smile:

I’m not sure what you mean. I package it using the “Package for QGIS” icon. I can’t find anywhere where I could select anything else.

Welcome to the forum, @ZahnKurt !

I do what you describe every day for many layers. Here is an example setting (the second applies, “cable packaging action”, since I do not go via QFieldCloud).

Note that the plugin also brings a tab in the project settings where you have all layers at a glance.

This works for me both on postGIS layers with geometry, or plain postgres tables.
If that does not work you, despite setting the options, I would guess there is an issue one level higher: double-check the basic map layer configuration to make sure it is really connected to postgres. In particular, check everything in the “Data Source Manager” ([Ctrl]+[L]).

Thanks, I completely restarted everything, and now it works. I actually did exactly the same thing as before, so I have no idea what the issue was. :smiley: