Sorry, we didn't find any relevant articles for you.

Send us your queries using the form below and we will get back to you with a solution.

Data Validation

Topics on Data Validation

Datatools/Kleber

1. Can we change the Kleber endpoint? Yes, you can enter the end point in the "Ad ...

1. Can we change the Kleber endpoint?

Yes, you can enter the end point in the "Address Helper URL" field on the Merchant Facility.

 
 

SOQL error when updating address fields

This is regarding the following error that occurs when trying to update address o ...

This is regarding the following error that occurs when trying to update address of an account (or contact) using the ‘Address update’ buttons.

Payments2us has the following buttons:

  • On Account - named “Billing address update” and “Shipping address update”.  
  • On Contact - named “Mailing Address Update” and “Other Address Update”.

They have been updated recently. The new ones reference Visualforce pages and the ‘Button or Link URL’ includes an “L” before the account/contact id:

The two scenarios of getting this issue are standard buttons or custom buttons. For both the solution is: Please check that the ‘Button or Link URL’ is following the same format as below and has the ‘L’:
/apex/AAkPay__AccountAddressL?id={!Account.Id}

Refer to following article for steps on how to create a button.

 

Why am I getting the error with program area: dataToolsKleberUtil.GenerateTemporaryRequestKey

This is most probably due to Data tool service having some API issues on their en ...

This is most probably due to Data tool service having some API issues on their end, because of which if you are using their service then you can get this error message. However, they would have fixed the issue and should now be operating normally. For more information on their downtime, please see Past Incidents in the following status page from Datatools: https://status.datatools.com.au/

It is advised to register for the updates on the above link so you can stay up to date with such issues.

If you do continue to get the same error, then please reach out to us and we can have a look further.