- Check the Error log - see if there are any errors in the import fields.
- Check Apex Jobs within Setup - see if the import has been completed.
- Check that the Demo Merchant Facility has the correct Org ID for the Sandbox in it, not the copied ID from Production. These need to match in order for the batch processor to function, so if you do not want to charge the transactions make sure that you use the Sandbox Org ID instead of the ID from Production.
Please proceed with caution if you have copied your LIVE Merchant Facility to Sandbox
Please note: Do not use your LIVE Merchant Facility copied into Sandbox for test, always use the Demo Facility. Otherwise there may cause duplicate charges. For extra security, remove the Payment Gateway password and deactivate the LIVE Merchant Facilty. - Check for any custom fields added that they do not have "duplicate" API names . Salesforce processes remove the AAK from the API name and will read it as a duplicated eg: AAK_firstname__c is recongnised as have the same API name as firstname__c. It will however allow for new custom objects to names and will not return with errors when creating new fields. We are endeavouring to address this in conjunction with Salesforce.
Sandbox
Topics on Sandbox
I'm trying to import a file in sandbox, but no records are being created even though it has the status Completed.
Check the Error log - see if there are any errors in the import fields. Check Ape ...
I have created a new Full or Partial Sandbox, what do I need to do to make things work?
You may need to update the Salesforce Org Id on the Merchant Facility. PLEASE use ...
- You may need to update the Salesforce Org Id on the Merchant Facility. PLEASE use extreme caution and follow the notes in The Merchant Facility FAQ - How do I test in Sandbox with my Merchant Facility copy, but make sure it does not start charging cards in my live instance by mistake?Â
- Make sure you reset your Base Site URL on the Merchant Facility. See procedure "How to connect your new site to your Merchant Facility"
- Re-Authorise Payments2Us App. See procedure "How to authorise Payments2Us for Public Website"
- If you are using License Options for Payments2Us add-on's, email support @ payments2us.com your Salesforce Organisation Id and request updated license keys.
- We recommend updating ALL payment gateways that are live and remove the password. This is to stop accidental charging of live cards.
- If your sandbox includes Recurring Payments, we recommend clearing out all Billing Token and Customer Payment Gateway Profile Ids on the Recurring Payment Object.
Can we push Payment forms and Merchant Facilities created in Sandbox to Production?
It is not possible to push to production. The safest way is to recreate the forms ...
It is not possible to push to production. The safest way is to recreate the forms in Production.
You could potentially use data loader to migration Merchant Facility, payment form, payment options, letter objects and re-link.
Note, on the Merchant Facility, there is the Organization Id field. You'd need to update that too.
If you've done a number of changes using the Payment Form builder, you could add the Payment Form JSON to the page layout and then copy/paste that to the production version.
Why I am not receiving an email when a Workflow is set to trigger an event, while working in Sandbox?
Because "Email Deliverability" will be turned off when a new Sandbox is created. ...
Because "Email Deliverability" will be turned off when a new Sandbox is created.
Am receiving this error when i try to open Merchant facility "ui.services.connection.api.PartnerConnectionException: INVALID_CROSS_REFERENCE_KEY: Master Encryption Key 1 has already been deleted"
After creating a full/partial sandbox, when i login to the sandbox and try to acc ...
After creating a full/partial sandbox, when i login to the sandbox and try to access my Merchant facility, i receive the below error “ui.services.connection.api.PartnerConnectionException: INVALID_CROSS_REFERENCE_KEY: Master Encryption Key 1 has already been deleted”
To fix the issue you need to open a case with salesforce and requesting them to enable the feature "Enable Encrypted Custom Objects in Full-Copy Sandboxes." They will ask for the production org ID and Admin username to enable this feature.
This feature needs to be enabled on the production org and then once it is enabled, you will need to refresh your Sandbox.
Payments2Us Upgrade Fails or Sandbox Not Updated After Upgrade
In a rare case, Payments2Us upgrade may fail or appear not to update a Sandbox(or ...
In a rare case, Payments2Us upgrade may fail or appear not to update a Sandbox(or Production) environment. This article explains the symptoms, root cause, and the required resolution.
Â
1. Symptoms, Root Cause, and Important Clarification
Common Symptoms
- Payments2Us upgrade fails during installation
- Sandbox remains on the old version after an attempted upgrade
- No visible changes after refreshing or logging back into the Sandbox
- Some users might receive an installation failure email
Typical Error Message (Example)
Some users may receive an automated Salesforce email similar to:
Your request to install package "Payments2Us" was unsuccessful. One or more components in the package failed deployment.
Problem: ReportFolder (Payments2Us / Fundraising) record deleted.
Not all users receive this email. In many cases, the only visible symptom is that the Sandbox is not updated.
Root Cause
This issue occurs when managed package “report folders” were previously deleted in Production and later copied into a Sandbox via refresh or recreated manually.
Although Salesforce should prevent deletion of managed package folders, this can rarely happen. Manually recreated folders may look correct but lack the original managed package namespace, causing the upgrade to fail when Salesforce attempts to validate or recreate them.
Note: This issue Is Rare and has only been observed with one customer so far. Again, most organisations never encounter it because managed package folders are typically not removed.
Â
2. Resolution and What to Tell Salesforce Support
The only confirmed resolution, which was provided courtesy the effected customer, is to contact Salesforce Support and request restoration of the original managed package report folders from archive.
Salesforce has internal tools that allow them to recover deleted managed package folders with the correct namespace and identifiers. Once restored, the Payments2Us upgrade can proceed successfully.
When contacting Salesforce Support, explain that:
- A managed package upgrade is failing or the Sandbox is not updating
- The failure references deleted managed package report folders
- The original folders need to be restored from Salesforce archive using internal recovery tools
Following is a list of folders (with hierachy and api names) to provide to salesforce if needed
- Payments2Us Reports - API Name:
Payments2Us_Reports- Fundraising - API Name:
Fundraising - Regular Giving - API Name:
RegularGiving - Financial Year - API Name:
FinancialYear - Campaign - API Name:
Campaign - Calendar Year - API Name:
CalendarYear
- Fundraising - API Name:
- Payments2Us In Page Reports - API Name:
Payments2Us_In_Page_Reports
Note: you will probably have to provide the org ID, user and package name (payments2us). If available, provide the deployment error number shown during the failed upgrade to help Salesforce trace the issue.
Â
3. Summary
- If your Sandbox is not updated, the upgrade may have failed silently
- This issue is caused by deleted or altered managed package report folders
- Manually recreating folders does not reliably resolve the problem
- The issue is rare and not caused by Payments2Us configuration
- Salesforce Support must restore the original folders from archive
- Once restored, the Payments2Us upgrade completes successfully (if upgrade was not manually done, reach out to inform payments2us support)