local-it/mitgliederverwaltung
2
3
Fork 0
Code Issues 72 Pull requests 3 Projects 4 Releases Packages 1 Activity Actions

[FEATURE]: Import custom fields for members #338

New issue
Open
opened 2026-01-07 14:01:05 +01:00 by carla · 0 comments
carla commented 2026-01-07 14:01:05 +01:00
Owner
Copy link

Description

Support importing custom field values from CSV columns. Custom fields should exist in Mila before import for best results.

Important Requirements:

  • Custom fields should be created in Mila first - Unknown custom field columns will be ignored with a warning message
  • CSV headers for custom fields must match the custom field name exactly (same normalization as member fields applies)
  • Custom field values are validated according to the custom field type (string, integer, boolean, date, email)
  • Unknown custom field columns (non-existent names) will be ignored with a warning - import continues

Tasks:

  • Extend header_mapper.ex to detect custom field columns by name (using same normalization as member fields)
  • Query existing custom fields during prepare/2 to map custom field columns
  • Collect unknown custom field columns and add warning messages (don't fail import)
  • Map custom field CSV values to CustomFieldValue creation in process_chunk/3
  • Handle custom field type validation (string, integer, boolean, date, email)
  • Create CustomFieldValue records linked to members during import
  • Update error messages to include custom field validation errors
  • Add UI help text explaining custom field requirements:
    • "Custom fields must be created in Mila before importing"
    • "Use the custom field name as the CSV column header (same normalization as member fields)"
    • Link to custom fields management section
  • Update CSV templates documentation to explain custom field columns
  • Add tests for custom field import (valid, invalid name, type validation, warning for unknown)

Acceptance criteria

  • Custom field columns are recognized by name (with normalization)
  • Warning messages shown for unknown custom field columns (import continues)
  • Custom field values are created and linked to members
  • Type validation works for all custom field types
  • UI clearly explains custom field requirements
  • Tests cover custom field import scenarios (including warning for unknown names)

External or internal Dependencies

#334

## Description Support importing custom field values from CSV columns. Custom fields should exist in Mila before import for best results. **Important Requirements:** - **Custom fields should be created in Mila first** - Unknown custom field columns will be ignored with a warning message - CSV headers for custom fields must match the custom field **name** exactly (same normalization as member fields applies) - Custom field values are validated according to the custom field type (string, integer, boolean, date, email) - Unknown custom field columns (non-existent names) will be ignored with a warning - import continues **Tasks:** - [ ] Extend `header_mapper.ex` to detect custom field columns by name (using same normalization as member fields) - [ ] Query existing custom fields during `prepare/2` to map custom field columns - [ ] Collect unknown custom field columns and add warning messages (don't fail import) - [ ] Map custom field CSV values to `CustomFieldValue` creation in `process_chunk/3` - [ ] Handle custom field type validation (string, integer, boolean, date, email) - [ ] Create `CustomFieldValue` records linked to members during import - [ ] Update error messages to include custom field validation errors - [ ] Add UI help text explaining custom field requirements: - "Custom fields must be created in Mila before importing" - "Use the custom field name as the CSV column header (same normalization as member fields)" - Link to custom fields management section - [ ] Update CSV templates documentation to explain custom field columns - [ ] Add tests for custom field import (valid, invalid name, type validation, warning for unknown) ## Acceptance criteria - [ ] Custom field columns are recognized by name (with normalization) - [ ] Warning messages shown for unknown custom field columns (import continues) - [ ] Custom field values are created and linked to members - [ ] Type validation works for all custom field types - [ ] UI clearly explains custom field requirements - [ ] Tests cover custom field import scenarios (including warning for unknown names) ## External or internal Dependencies #334
carla added this to the I can import members milestone 2026-01-07 14:01:05 +01:00
carla added the
M
 label 2026-01-07 14:01:05 +01:00
carla added a new dependency 2026-01-07 14:01:51 +01:00
#334 [FEATURE]: Implement persistence via Ash Create
carla added this to the Sprint 11: 08.01-29.01 project 2026-01-08 12:53:24 +01:00
Sign in to join this conversation.
main
Branches Tags
Clear current reference
main
docs/update
speed-up-drone
feature/220_ui_issues_2
persist-sort-order
feature/151_roles_permissions_docs
manual_renovate_update
feature/#158-polish-README
feature/128_playwright_a11y_test
feature/119_member_user_relation_refactor
feature/119_user_as_member
feature/backpex-migration
feature/backpex_translation
feature/39_account_ressource
feature/74_memberfields
validation
feature/36_add_primerlive
Clear current reference
No results found.
Labels
Clear labels   
bug

Something is not working

  
duplicate

This issue or pull request already exists

  
enhancement

New feature

  
help wanted

Need some help

  
high priority

   
invalid

Something is wrong

  
L

5 h

  
low priority

   
M

3 h

  
medium priority

   
needs refinement

   
optional

   
question

More information is needed

  
S

1 h

  
UX research

   
wontfix

This won't be fixed

No labels
bug
duplicate
enhancement
help wanted
high priority
invalid
L
low priority
M
medium priority
needs refinement
optional
question
S
UX research
wontfix
Milestone
Clear milestone
No items
No milestone
I can import members
Projects
Clear projects
No items
No project
Sprint 11: 08.01-29.01
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Depends on
#334 [FEATURE]: Implement persistence via Ash Create
local-it/mitgliederverwaltung
Reference: local-it/mitgliederverwaltung#338
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?