Uploaded image for project: 'CiviCRM'
  1. CiviCRM
  2. CRM-952

Export - Primary export should NOT include custom fields

          Details

          • Type: Improvement
          • Status: Done/Fixed
          • Priority: Major
          • Resolution: Fixed/Completed
          • Affects Version/s: None
          • Fix Version/s: 1.5
          • Component/s: None
          • Labels:
            None

            Description

            Currently, when you do a "Primary fields" export - we include core contact fields (contact, individual, org, household), plus location fields PLUS all custom fields. This causes problems when users have defined large numbers of custom fields (they will get "exceeded max number of joins errors...").

            Modify this export mode to eliminate exporting of custom fields. Also, any additional component-defined fields (e.g. Quest/Student) should NOT be included in this mode (folks will need to use the "Select fields for export" mode to output these fields).

              Attachments

                Activity

                  People

                  • Assignee:
                    deepak Deepak Srivastava
                    Reporter:
                    dgg David Greenberg
                  • Votes:
                    0 Vote for this issue
                    Watchers:
                    0 Start watching this issue

                    Dates

                    • Created:
                      Updated:
                      Resolved: