In 9.05, there's a "File System Document" attachment type that actually uploads the file to a share rather than just linking to the file location. That's what I'm using.
I've got a Pre-Process Directive that bails on the method, and I've verified that it doesn't create an XFileRef/XFileAttch record, but it still uploads the file. So now I've got an orphaned file on the server w/ no record in Epicor to tie it back to...
Anyone else using File System Documents?
I've got a Pre-Process Directive that bails on the method, and I've verified that it doesn't create an XFileRef/XFileAttch record, but it still uploads the file. So now I've got an orphaned file on the server w/ no record in Epicor to tie it back to...
Anyone else using File System Documents?
--- In vantage@yahoogroups.com, "jckinneman" wrote:
>
> Are you using something other than standard file attachment? Standard file attachment only stores the file location, it doesn't actually do anything with the file.
>
> Jim Kinneman
> Encompass Solutions, Inc
>
> --- In vantage@yahoogroups.com, "cubcrafters_it" wrote:
> >
> > When attaching a file to a receipt, the Receipt.UpdateMaster method is called and sends the file path to Epicor.
> >
> > I can hobble together BPM code to prevent the XFileRef and XFileAttch records from being created, but it doesn't stop the file from getting uploaded to the file share.
> >
> > Does anyone know how to prevent the uploading from happening?
> >
>