Skip to Content
Technical Articles
Author's profile photo Sandip Biswas

SF Release 1811: Identified Issue for Employee Central Payment Information & Solution

Background: After 1811 release in our preview instances we were facing issue in the Employee Central Bank Information portlet. There is a pre-delivered SF standard rule “setMainBank_PaymentInfo” which was added on Object “PaymentInformationV3” for field “jobCountry”. This rule defaults certain fields (like Payment Type, Payment method, Account Owner, Bank Country & Currency) in the Payment Information portlet when employee wants to create/edit any payment information.

Technical Detail on the rule:

Object: PaymentInformationV3

Field: jobCountry

Onselect Rule: setMainBank_PaymentInfo for field jobCountry.

Issue after 1811 release: For an employee if there is already existing Payment Information record & employee wants to edit the existing record then duplicate bank record line item is appearing for main payment method which is throwing error message during saving the payment information data.

Existing Sample Data for an employee:

After clicking Edit: Duplicate entry is appearing for Main payment method.

As there are two different line items/records for Main payment method, system will give error message at the time of saving the data.

Resolution: There are couple of options to resolve the issue.

Option 1: Remove the rule from the field jobCountry but here system will not be able to default the fields, during creation of new Bank Record which will impact existing functionality.

Option 2: We can do a small modification in the standard delivered rule. To do it, first copy the rule & then amend the if condition of the copied rule. Add a condition as per below screen. After that replace the SF standard rule with the newly copied one.

Result: The system is behaving correctly.

Also there can be other solution/solutions for that issue.

Conclusion: If you are using the standard rule “setMainBank_PaymentInfo” for field “jobCountry” in object “PaymentInformationV3” in your production instance then follow the above steps until there is a permanent fix for it.

Assigned Tags

      Be the first to leave a comment
      You must be Logged on to comment or reply to a post.