SalesforceFoundation / NPSP

The current version of the Salesforce.org Nonprofit Success Pack
http://www.salesforce.org/nonprofit/nonprofit-success-pack/
BSD 3-Clause "New" or "Revised" License
16 stars 3 forks source link

BDI: Clone or Edit of NPSP DataImportBatch fails when not created through Gift Entry / BGE #5637

Closed ptewson-sfdo closed 2 years ago

ptewson-sfdo commented 4 years ago

Attempting to either clone or edit a NPSP DataImportBatch record results in the message "SObject row was retrieved via SOQL without querying the requested field: npspDataImportBatchc.npspRun_Opportunity_Rollups_while_Processingc "

Steps to reproduce:

  1. Log in to Salesforce
  2. Visit the "NPSP Data Import Batches" tab
  3. Create a new batch, Name = "Test Batch Clone or Edit" (Do NOT select the "Gift Batch" checkbox if available)
  4. From the related list on "NPSP Data Import Batches" home, click the record link to view your newly created batch
  5. Hit the "Clone" button in the upper-right of the page

EXPECTED: Clone the record

ACTUAL: Message "SObject row was retrieved via SOQL without querying the requested field: npspDataImportBatchc.npspRun_Opportunity_Rollups_while_Processingc"

image

bmdelaune commented 4 years ago

+1 Looks like BDI_SettingsUI.component requires the field Run_Opportunity_Rollups_while_Processing__c but its not added in the controller BDI_BatchOverride_CTRL.cls

shippconsulting commented 4 years ago

There is a relatively quick workaround for this. Do the following:

  1. Create a flow with an input screen that contains the fields you want to update. I my case it was the Donation and Contact matching rules. (variable called recordID, Get Record to get NPSP Data Import Batch Record, Screen with the fields you want to update, Update Record to update the fields as changed on the screen)
  2. Create an Action button to call the Flow.
  3. Add flow to the page layout.

This can be done in 10 minutes. Beats having to use Workbench to update the data.

Good luck!

kporray1 commented 2 years ago

This issue is no longer being considered by the product team.