using ECM 23.1.62 and installed the V2 AP Automation integration datalinks, entered the required settings and tested a few of the lookup datalinks and they are working.
You get a message to do the “Get Updates”
“Some queries on this integration require getting their parameters live. Please confirm the settings are correct and click the ‘Get Updates’ button.”
When I do this I get an error - Object reference not set to an instance of an object
Raised an issue with support and they were useless and just closed it saying speak to consulting.
Yes. It kinda sucks the way Epicor has this set up for support. Contact your CAM and ask them to get you in touch with the ECM Pro services guys. They create & manage the delivered workflows and will (should) help you resolve this under your support contract. the fine line is that support will not help with workflows because it’s considered custom code. But the PS guys have to help make the API calls work because it’s THEIR code.
We had this happen when a field name was already used(ours) and was different TYPE then the field the workflow update was trying to create. It may also happen with the AP Workflows because they had some issues lately with Legal Numbers - I suspect they are pushing the updates out now to change the API calls used by the workflows.
Neil, are you liking the new APv2 workflows? One thing I am hoping gets better is the integration between deleting a document and having it delete the invoice out of a batch- or just the whole “DS” group in general. That, “work in process” invoice group that it creates right now in the v1.
I’m not using the V2 workflows, I have taken some elements from the V2 workflows i.e. Auto match and added some v2 datalinks (replaced v1 datalinks), to my customised workflows. Some datalinks are better, but I’m finding that some are missing basic fields - which means I can’t use them or have to add extra steps to get everything we need.
For deleting documents in ECM and the AP Group, I have a process where the users - move the document to a workflow - that removes it from the AP group and then deletes the document from ECM. If they dont follow this, we also have an ECM form, that they can use to delete invoices from the AP group.
Yeah, that’s the thing I wish was cleaner… you and me have to teach them to assign it to a workflow or use a form… I think the delete button should do something to the invoice in epicor (delete it) if it’s not posted, or throw warning when it is posted and you’re deleting an attached item.
the V2 workflow doesn’t use the temp DS group. It now has an API call for “Pre-Create” that sends all the invoice data and allows kinetic to accept/reject it and the workflow then stops there with the API error. If it takes it, the Invoice is in the group (name of your choosing still) but it never exists in two places!
And what about when you go to delete the invoice after it has been accepted? Or is “being accepted” the end of the workflow… no turning back after that?
I’d have to make 100% sure, but nothing is permanent until someone posts the AP group inside kinetic. Overall it’s better, and easier to debug since the invoice cannot be in anywhere but the workflow and/or the AP group. You can even call the Pre-Create multiple times if you add misc charges, GL lines, etc. and Kinetic will accept/reject based on the business logic.
When ECM creates the invoice in AP Invoice Entry it will be assigned a SysRowID. The v2 workflows have some initial steps to evaluate if this field is present and populated. If it is, then it will ask the user if they would like to delete the document. Choosing yes to this prompt will delete the document out of the associated AP group in AP Invoice Entry and then the workflow will continue. This is particularly helpful when having to restart or reassign the workflow.
On the v1 side, I have found it easy enough as an Admin to use the specific datalink to delete an invoice out of the DS group as it isn’t always easy to access directly in Epicor. I’m sure a similar process to v2 could be created for v1, but the temporary group does add a level of complexity to navigate.
To the best of my knowledge, all that the Actions Menu > Delete option does is delete the document out of ECM. It will not delete the attachment link in Epicor and will therefore cause a phantom/broken link in Epicor.
By default, the SysRowID field being evaluated is only part of a workflow that comes with the AP Automation license. A different field is evaluated for SO Automation, but the same premise applies.