Pay method setting?

So, we are noticing that ECM does not seem to be hitting the method for OnChangeVendBankID. I’m assuming it’s using updateEXT so it doesn’t hit it. Because of that, it’s not changing the pay method based on the Bank Id (Remit to). That’s a problem.

So I though, Ok, I’ll set in on the create invoice datalink and set it explicitly, since there are spots to set it.

I’m getting that from a datalink SQL call. That part is pulling the correct information.
image

Well, that doesn’t seem to be working, and I don’t know what I’m missing.

Does anyone have any experience with trying to set the pay method on the create invoice integration point?

This sounds very familiar.
Are you multi-company?

Can you update it with a REST call in REST only? I find sometimes an updatemaster or updateext RPC call can help with updates after the invoice creates.

Other options, try the create datalink in the integration tab with all information filled in, see if you can fill in the pay method fields and if it updates correctly, if that doesn’t work, then it probably needs an update after create as described in the 1st paragraph of my reply.

@Anthony_Gercar , we are multi company, although everything that I am doing is is one company.

@swilliasc111 I haven’t tried making any other calls yet. I was hoping to keep the complexity out of it and not have to make another call. (If I’m understanding what you mean)

1 Like

Through all of my testing with both the Pre-Create and Create datalinks, I’ve found that while they can each do a lot of things to make changes to the different fields listed, they cannot do all of the changes at the same time. The best way I can understand it is that even if you were to manually do things in Epicor, you can’t change the payment method at the same time that you change a dollar value at the same time you change a line item at the same time you change a… etc.

Effectively, we can send in a complete set of commands through these datalinks, but there is little in place to push all of the specific data through iteratively so it essentially tries to do everything at the same time, which always causes issues. The basic creation of header details and then line details is about as complex as I’ve seen it function to create things in order.

To combat this, I have often had to run the datalinks multiple times with different criteria selected to mimic the iterative process of things. You may need to run another Create, but this time remove everything but the essentials and the fields you wish to change.

I figured out what it was. :man_facepalming: . I was looking at the wrong field. It’s PMUID. Once I set that, it’s good. Information overload.

image

3 Likes