Hey Beth,
May I ask, why a network drive?
If you have 365, you may want to consider using a SharePoint Document Library. These can be sync’d back to local drives - if necessary. 
They also give you the added benefit of search, meta data, security, traceability, data loss prevention, etc. - features not easily accessible on a company’s Novell Network Share.
Hi Mark,
It’s because that is where all the invoices are stored currently when they have been input to Epicor. We are not completely on ECM for all of our invoice types, but will be by the end of the year. This will all become a moot point when that happens. For now, AP doesn’t want half in ECM and half on the network drive (it’s too tough for them to handle that), so they requested a way to save automatically to the K drive when it’s processed through ECM.
Beth
I think they could attach the document to the invoice from invoice entry as a docstar document and then it would be in ECM and in the file share the same way it is now, would that work?
I see. Can you place them in a folder at the ECM client and have the client copy it to the K: drive after being imported to ECM? You just need the XML file to give it the invoice number, customer number, etc.
BTW, it is possible to pull reports down from Kinetic using PowerShell. This is just an proof-of-concept if you know the SysRowId, but that could be looked up. You don’t have to push things through ECM, you can pull them too.
// Get Epicor Credentials. Boo. Use token auth instead.
$pscred = Get-Credential
$headers = @{ 'accept' = 'application/json'
'Content-Type' = 'application/json'}
$rpt = ConvertTo-Json(@{ sysRowId = 'SysRowId here'})
$result = Invoke-RestMethod -uri "https://server/instance/api/v1/Ice.BO.ReportMonitorSvc/GetReportBytes" -Method Post -Credential $pscred -body $rpt -Authentication Basic -Headers $headers
$filename = "path to K: drive with file name"
// Convert back to binary
$bytes = [Convert]::FromBase64String($result.returnObj)
// Write file to disc
[IO.File]::WriteAllBytes($filename, $bytes)
You could use a script like this to pull down the invoice, copy it to the input folder for ECM, then also copy it to the K: drive. Or let APS send it to ECM and then use this to copy to the K: drive afterwards. You have options.
Wait. These are AP invoices. Since they are already PDFs, you should be able to use the ECM client to load them, no?
No, you can’t from ECM. There is a manual way to export but not an automated way 
Not export, but import. I seem to recall that the ECM client can run a post process and you could copy the file to the K:.
BTW, I may not be understanding the workflow.
Ah, so you are saying that when we import the document to IDC, then copy it to the K drive as well, correct?
That may work too. I’m not familiar with IDC, but at some point you have to import into ECM. That’s where I think you could shim in the copy. @MikeGross or @gpayne would know for sure.
Sorry I was not following this since it involved math. There are several ways to do this easy, slight of hand and really cool.
Easiest is direct the on completion folder which is usually a sub of the import folder to the K drive subfolder.
Slight of hand. Share the processed folder and map that to a subfolder on the K drive or XCopy the processed folder to the K drive processed folder.
Cool: This week @utaylor showed me how to successfully make a rest call from ECM which opens up your PS idea or I have a UBAQ that moves a file, so something like that could be used. Yes, he beat me and @MikeGross to rest in ECM and his works and mine is just a couple of tests.
@Beth , @Mark_Wonsil is right in that the batch import process in the ECM client has a ‘move to’ operation, post import. You could import and ‘copy’ in the same motion. That is, assuming the device/user running the client has access to the shared location either by drive map or UNC path.
We had help with a starting example from a consultant*
But yes, it did take some trial and error and personal knowledge to transform the example so I think we deserve a little credit haha!
@MikeGross, I like the clever workaround that you, @Beth & @Mark_Wonsil are discussing.
I don’t want to annoy anyone, but I wanted to share my own perspective: The solution to import from IDC to ECM and ‘copy’ to a network folder in the same motion would not be ideal in my situation for 2 reasons:
But FYI – I’m not seeking a workaround that meets my needs. So please stay focused on @Beth 's needs.
Very much agree! Attaching to the batch import process would be prior to any workflow logic and would certainly fail in your example situations. Thanks for pointing that out!
Once you are in the workflow, the Automation Studio or REST calls would be the way to go.
Thank you, everyone for your input! Lots to think about and decide what will work for us best. Right now, I have created a “title” for the document in the format that AP wanted to see it. They probably want the file to have the same name as the Title, so that will determine the way we accomplish the task.
Beth, I asked this earlier too, but why can’t they follow their normal practice and then drag and drop the attachment into invoice entry as an ECM attachment?
Utah, It’s because they want the process as automated as it can be so they don’t make mistakes.
I see what you are saying, so they don’t want to do any attaching at all.
No, they don’t. Just like everything, it’s complicated 
Added an idea for better guidance of the Advanced Math task:
https://epicor-ecm-docstar.ideas.aha.io/ideas/ECM-I-1163