hello, i am getting the error “row already belongs to another table” when trying to select jobs to adjust global scheduling order. has anyone had this error and how to fix it?
1 Like
If the error comes from a bpm, you can fix it, if not that sounds like you need to open a ticket. Can you provide more detailed info on the error?
1 Like
it is when i open adjust global scheduling application and search for jobs to adjust the scheduling order on. it seems to be specific jobs it is erroring on. i had been trying to create a BPM/Function to systematically update the scheduling order on unfirm jobs but with out much luck. so i had refreshed by test environment from live, so the things i was trying to do aren’t there anymore. I ran global scheduling order and then when i was trying to adjust it it wasn’t working.
1 Like
You should be getting a correlation ID that is a GUID when you get this error, you will want to go to server file download, grab the latest log from server, and search within it for correlation id (or if you don’t have that - look for the error above “row already belongs to another table”) there should be some more error detail in the server log around here.
1 Like
yes, i have that correlation ID. is there a normal spot that the server file download lives? we are on prem.
1 Like
wow, sorry it is a monday. i found what you are talking about
3 Likes
All good, glad you found it
so i submitted a ticket with EpicCare, and the response i got was that it is related to a known problem that is fixed in the versions 2025.1, 11.3.200.X (2024.2), and 2024.1.21. we are currently on 2024.1.19 so that isn’t that helpful.
2 Likes
If you are live on a version that does not have the fix, and no plans to upgrade to a fixed version, my suggestion would be to submit a request for a hotfix for your version, in the same ticket.
If it is a supported version, Epicor should backport the fix. Escalate if you have to!
1 Like
good to know, thanks for letting me know that is possible