Unless Foxit Reader’s search functionality is absolute trash, the terms, “attachments”, and “attachment”, exist nowhere in the Epicor Installation Guide.
Where might I be able to configure where the file attachment path location should be in a v10.2.700.X install, because it doesn’t exist where I had expected it to be:
I assume you have the proper rights to it, yeah?
I’m on 10.2.600 and I see it there (as well as Kinetic 2021.1.7), so you should definitely have it in your version.
Ohhhh, gotcha!
Hmm, I’m not sure that’s within the scope of the install guide.
It was probably in the release notes/change log, though, trying to sift through that–oof.
So - this was what I was concerned about with “transitioning” the file attachments (because I have no references/guides):
The above screen cap is a depiction of an error that occurred after I created a new directory structure for file attachments (because the old one, in terms of nomenclature, doesn’t fit how we’ve named the new app server), then copied ALL of our files from the old attachments directory to the new one.
I’m going to rename the new directory structure to what the old one currently is and see what happens.
So - I merely recreated/duplicated the exact same directory structure on the new Epicor server, then copied the entire file attachment library by the company folder into the duplicated directory and tested opening a few file attachments from different modules.
Pros: Simple, easy to transition your file attachments
Cons: You cannot change anything about the nomenclature of the directory structure, even if you have a spelling error on a folder, or if you’ve decided to name your Epicor application server in a different way.
You’re talking about the File System attachments here, so there are other cons, like security is much harder to manage than a DocStar. The SharePoint implementation is too much like the File System so it’s difficult to do security like DocStar.
The Link storage type just needs a URL to the file so one could use SharePoint or Blob Storage, and get the full capabilities that goes with those services.
I was doing a quick test to see if I could simply DMT a new file path into the “XFileRef” table, listed in DMT as:
… and that seemed to work.
I logged back into the client after the DMT process completed and was able to open a number of file attachments directly from the file attachment trees of a random sample of Epicor tracker modules.
One interesting note: out of over 40,000 file attachment records, only 16 had errors and they all had to do with ----> “File name too long. Limit is 183 characters.”
<comedic_code>
foreach (Hole) {
if (Existing.Knowledge == "No Clue") {
Dig;
}
if (Existing.Knowledge == "EnhancedByEpiUsersHelp") {
Fill;
}
}
</comedic_code>
I keep digging holes and you guys keep making me fill them back in!
Thanks for this suggestion, Greg! Never knew this maintenance module existed.
I’ll play around with that tomorrow and see how it works.
Very helpful, indeed.
Hasn’t even been on my radar during upgrades.
Mostly because we use links/refs to network locations.
We just stop use links/refs for file attachment last month. Too many people linked the files then go to the network shared folder and change/move the files. Then when the users click on the links / file attachments in ERP, they are broken
With the file upload, no more broken links
One interesting note: out of over 40,000 file attachment records, only 16 had errors and they all had to do with ----> “File name too long. Limit is 183 characters.”
