Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
C
Core
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 918
    • Issues 918
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • Development
  • Core
  • Issues
  • #1204

Closed
Open
Opened Aug 23, 2019 by yashodha@yashodhaDeveloper

Data import for custom membership fields is done as text Instead of value

Data import for custom membership fields is done as text Instead of value. The same works for contact custom data.

Steps to replicate :

  • Create a custom data used for Membership having Data Field with Alphanumeric and Field Type Autocomplete-Select
  • The values in the look up should be numeric.
  • Try to update the membership record using import for the custom field with text not the value.
  • Check the field in DB, the data is imported but stored as text not value - so this doesn't show up in the UI.

I was able to replicate this on dmaster.

Option value optio

Import

import

Final value in database mem_Record

Edited Aug 23, 2019 by yashodha
To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: dev/core#1204