When we need a datafix, it’s often at least a semi-urgent need. Support has to be contacted, walk thru the scenario with them if it’s the first time, support submits issue to dev team, dev compiles the fix, it gets uploaded to the case, we download, install, then run it. And all the details are hidden inside an encrypted file that only works for the company requested, and it has a time-based expiration.
Why isn’t there more general access to datafixes? Especially for more benign fixes. Let me download what I need, give me documentation on what they do and when to use them.
Why are the expirations time based? They are only valid for the current version, so why not just allow them to be perpetual for that version, or at least through your current contract date?
Example - we used to have an issue with MRP runs that would hang up or die. The task record for Process MRP still existed in the database, so we needed a datafix in order to delete the task record prior to being able to run MRP again (as a cloud customer, we have since found it’s easier to build a workaround BPM to delete the record). But that datafix would last X days, and of course you don’t know until it’s expired that issue happens again, and you need to re-request. → what should take a few minutes often takes several hours. Meanwhile the team waits.
Today we have a new issue where we understand what datafix is needed and can call it out by name (thanks EpiUsers!), but our entire procurement team is on hold while support goes through the hoops to get it delivered.
The whole process seems unnecessarily complicated. ![]()
