Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
dracic opened this issue Apr 16, 2021 · 2 comments
Labels
enhancement New feature or request

Comments

@dracic
Copy link
Contributor

dracic commented Apr 16, 2021

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
Copy link
Contributor

Related to #5

@wonder-sk wonder-sk added the enhancement New feature or request label May 6, 2021
@dracic
Copy link
Contributor Author

dracic commented Jun 14, 2021

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants