search

MerginMaps / work-packages

Mergin Maps Work Packages: manage field surveys for multiple teams
MIT License
7 stars 4 forks source link

New features from different teams should have filter-column automatically populated #22

Open dracic opened 3 years ago

dracic commented 3 years ago

New features from different teams should somehow have filter-column automatically populated with team values if emtpy, and that is not the case at the moment. If this doesn't work this way, after data sync you have records from all teams in each package.


tables:
  - name: farms
    method: filter-column
    filter-column-name: survey_team

work-packages:
  - name: TeamA
    value: A
    mergin-project: My Company/Survey Team A
  - name: TeamB
    value: B
    mergin-project: My Company/Survey Team B

So if I'm on A team and if I add a new farm, shouldn't column "survey_team" be somehow populated with value "A"? If not immediately than on next work-package sync.

wonder-sk commented 3 years ago

Related to #5

dracic commented 3 years ago

As I now use overlay functions for default values in filter columns od recording layers, I really don't know why I wrote this. It is not an issue that cannot be resolved with carefully created projects.