Answers.Body: <p>I think this <a href="https://github.com/civicrm/civicrm-core/pull/26262" rel="nofollow noreferrer">was fixed</a> a couple weeks ago. Can you test it on master?</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2023-05-31T20:57:29.427Z
Answers.Text: Happy to try but don't know what "master" is. But, also, the fix seems to refer to the other similar question, where the "save fields" button is missing. I have that, but it gets stuck later. But maybe this is because I have quite an old version of CiviCRM
Answers.UserDisplayName: Mick Kahn
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2023-05-31T22:13:46.020Z
Answers.Text: Do you have a test site that you could try the very latest code for CiviCRM on (master)? Normally you could just check something like this on the demo site (https://dmaster.demo.civicrm.org/), but I don't think you'll be able to set up the permissions you need there. In any case, if it is now working in the most up to date version, I'd assume the fix will be to update your site when 5.63 comes out.
Answers.UserDisplayName: Lars SG
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2023-05-30T23:22:35.217Z
Answers.LastActivityDate: 2023-05-31T00:22:28.823Z
Answers.LastEditDate: 2023-05-31T00:22:28.823Z
Answers.UserDisplayName: Lars SG
Body: <p>As a CiviCRM admin, I have no problem saving field mappings for export, but it isn't working properly for non-admins. I can't see any permissions that might be missing (I don't want to give them full admin permissions). The problem showed up with exporting participants, but the problem is also there for contacts. All works fine up to the actual save but it then hangs with a spinning wheel on the final save button. I thought it might be the same as <a href="https://civicrm.stackexchange.com/questions/42881/what-permission-set-allows-a-user-to-be-able-to-save-a-field-mapping">What permission set allows a user to be able to save a field mapping?</a> but the symptons are different there in that they cannot see the save option at all.</p>
  <p>Using CiviCRM 5.35.1 on WordPress.</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2023-06-01T19:51:24.893Z
Comments.Text: When you Export, and when Non-Admins do an Export - are you both choosing specific fields,  or are you both using Primary Fields - or are you doing the former and they doing the latter? if the last option then i have a suggestion
Comments.UserDisplayName: petednz - fuzion
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2023-06-01T23:55:39.287Z
Comments.Text: Both chosing specific fields and I don't see how you would get an option to save mappings if you were just using primary fields.
Comments.UserDisplayName: Mick Kahn
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2023-06-02T01:50:44.373Z
Comments.Text: sorry yep read it too quickly and was thinking about the problems folk have had using Primary Fields in exports. you are right.
Comments.UserDisplayName: petednz - fuzion
Tags: <field-mapping>
Title: Problem saving field mappings for export
ThreadText: # Problem saving field mappings for export
  
  (Asked by: username_0 on 2023-05-30)
  
  As a CiviCRM admin, I have no problem saving field mappings for export, but it isn't working properly for non-admins. I can't see any permissions that might be missing (I don't want to give them full admin permissions). The problem showed up with exporting participants, but the problem is also there for contacts. All works fine up to the actual save but it then hangs with a spinning wheel on the final save button. I thought it might be the same as [What permission set allows a user to be able to save a field mapping?](https://civicrm.stackexchange.com/questions/42881/what-permission-set-allows-a-user-to-be-able-to-save-a-field-mapping) but the symptons are different there in that they cannot see the save option at all.
  
  Using CiviCRM 5.35.1 on WordPress.
  
  **Tags:** field-mapping
  
  > **Comments:**
  > **username_1**: When you Export, and when Non-Admins do an Export - are you both choosing specific fields,  or are you both using Primary Fields - or are you doing the former and they doing the latter? if the last option then i have a suggestion  
  > **username_0**: Both chosing specific fields and I don't see how you would get an option to save mappings if you were just using primary fields.  
  > **username_1**: sorry yep read it too quickly and was thinking about the problems folk have had using Primary Fields in exports. you are right.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_2 on 2023-05-30. Score: 0
  
  I think this [was fixed](https://github.com/civicrm/civicrm-core/pull/26262) a couple weeks ago. Can you test it on master?
  
  > **Comments:**
  > **username_0**: Happy to try but don't know what "master" is. But, also, the fix seems to refer to the other similar question, where the "save fields" button is missing. I have that, but it gets stuck later. But maybe this is because I have quite an old version of CiviCRM  
  > **username_2**: Do you have a test site that you could try the very latest code for CiviCRM on (master)? Normally you could just check something like this on the demo site (https://dmaster.demo.civicrm.org/), but I don't think you'll be able to set up the permissions you need there. In any case, if it is now working in the most up to date version, I'd assume the fix will be to update your site when 5.63 comes out.  
  
  ---
  
  