Set value for subsidiary on Payment using Go to record
hi experts,
I used function Go to record by workflow, I have a custom record as ‘Payment request’, i set up work flow to direct to creat Payment, but i don’t associate subsidiary’s customer from ‘Payment request’ to Payment ( I can set value Customer, but subsidiary is not, i have to select customer again on Payment, in this, Subsidiary display data what is associate with customer on ‘Payment request’ ). ( i did same with Customer deposit and I can set value Subsidiary for this transaction). Anyone know why?
Hi there,
I’m sorry to hear that you’re having trouble associating subsidiary’s customer from ‘Payment request’ to Payment. I can understand how that would be frustrating.
There are a few possible reasons why this might be happening:
-
Workflow customization: It’s possible that the workflow you’ve set up isn’t properly mapping the subsidiary’s customer field from ‘Payment request’ to the Payment record. This could be due to a missing field mapping or an incorrect formula in the workflow.
-
Field mismatch: The subsidiary’s customer field in ‘Payment request’ might not be the same field as the customer field in Payment. This could be because they have different names, data types, or even internal IDs.
-
Customization limitations: There might be limitations in the Go to record by workflow functionality that prevent it from automatically associating subsidiary’s customer. This could be a known issue with the system or a specific limitation of your custom record or workflow.
To troubleshoot this issue, I recommend trying the following:
- Review your workflow customization: Double-check the field mappings and formulas in your workflow to ensure they’re correctly mapping the subsidiary’s customer field from ‘Payment request’ to Payment.
- Compare field details: Compare the data types, names, and internal IDs of the subsidiary’s customer field in ‘Payment request’ and the customer field in Payment. Make sure they’re exactly the same.
- Check for known issues: Search for any known issues or limitations with the Go to record by workflow functionality, especially regarding custom records and customer associations.
Thank anil,
With Case 1,2. I don’t think so, because, I also set up Go to record to Customer Deposit, and It run. But with Payment it’s not.
It may be limited with go to record for Payment.
Type of customer on “Payment request” is customer, but Type of customer on “Payment” is entity. I think This is problem.
I want to find a solution but I don’t need use Script.
