Kinetic Attachments

Ever since the last update in late August, we have had trouble attaching PDFs to projects in our Kinetic screens (works completely fine in Classic). What typically happens is we will drag and drop onto the screen and then after we click “Attach”, it will just spin forever. The only thing we can do is close out of Project Entry. Things get weirder though. The first letter in our Project ID is determined by which type of project this is. We only get this issue with projects that start with the letter “C”. Oddly enough, every project that had been created before 2024 has this issue (except 1), but for projects created in 2024, the issue is more sporadic. Haven’t run into this issue with our other projects starting with letters like “E”, “F”, and “L” among others.

None of these issues existed before that last update so I figured I could check with EpicCare and have them take a look for anything that wasn’t set up right during the update. After several screenshots and a few video calls, there is still no resolution. Has anyone else struggled with this in their Kinetic screens? Project Entry is like 1 of 5 apps that we have been able to use Kinetic for so it would be a real shame if we moved that one back to Modern as well, but not sure if this will get resolved.

I’ve also started noticing this weird error that occurs randomly. I’ll drag and drop on one project and the slide out will display a different project.

1 Like

How are ur files hosted?

Are u on Prem?

I posted something a week ago about attachments panel performing weirdly

Links:

We are a Cloud customer and store our files via File System. It’s weird because I can see the attachment in our file system, but if I go back to Project Entry and open up the attachments pane, the document isn’t there.

I’ll have to see if maybe it’ll just take a really long time to attach. After reading the 2nd topic you sent, wondering if we haven’t waited long enough.

After trying to attach a PDF over 20 minutes ago, it’s still spinning…

1 Like

Jeezeee, that’s very unfortunate.

Be sure to raise a ticket with support. Fingers crossed we can all get to the bottom of this quickly.

1 Like

Oh I definitely did raise a ticket. Unfortunately all they told me was that it was an issue caused by our data and the way we created those projects (over a year ago). I just found it odd that we only started having the issue after that update went out.

2 Likes

I think you need to keep arguing. If it works in classic, and not in Kinetic then it’s a :beetle:

3 Likes

:beetle: nice! Need to start using that on the title of the thread if it’s about a :beetle:

3 Likes

Our files are served from a dedicated, on-prem, file server.

Same as us…

Any further progress on your support ticket?

No, I just bumped Epicor this morning, again.

Yeah we’ve had multiple posts with this issue in the last couple weeks, it sounds like a bug.

1 Like