Skip to main content

Resolve common issues after upgrading to COINS ERP+ v12.05

Troubleshoot unexpected behaviour, display errors, MIME type issues, validation changes and mobile access problems following an upgrade to Access Coins ERP+ v12.05.

After upgrading to Access Coins ERP+ v12.05, you may notice changes to how certain screens display, how files are handled, or how validation rules behave. This article covers the most commonly reported post-upgrade issues and the steps to resolve them.

📌Note: Before troubleshooting, confirm your environment meets the v12.05 prerequisites: Progress OpenEdge v12 is required. If you are not hosted by Access Coins, M1x v4.5.0.0 is also required. Raise a support ticket if you need help confirming your environment version.


Display errors and unexpected screen behaviour

Some users report blank sections, layout shifts or unexpected content appearing on screens after upgrading. These issues are most commonly caused by cached browser data or browser compatibility.

Clear your browser cache

  1. Close COINS ERP+.

  2. Clear your browser cache and cookies. In most browsers, press Ctrl + Shift + Delete, select All time as the time range, tick Cached images and files and Cookies, then click Clear data.

  3. Reopen COINS ERP+ and log back in.

  4. Retry the screen or action that was displaying incorrectly.

Check your browser version

v12.05 has updated browser compatibility requirements. If display issues persist after clearing the cache, confirm you are running a supported browser version. See Coins Construction Cloud Supported Browser Versions for the current list.

📌Note: If you access COINS ERP+ through Citrix or a remote desktop, the browser version on the server applies — not the one on your local machine. Contact your IT team to confirm the server browser version.

Resolving blank screens and clearing user settings

If a screen remains blank after clearing the cache, your user settings may need to be reset. See Resolving blank screens and clearing user settings for steps to clear personalised layout settings that can conflict with the upgraded version.


MIME type errors when uploading files

v12.05 includes changes to how COINS ERP+ analyses and validates file types on upload. If you receive a MIME type error after upgrading, the file type may no longer be in the permitted list for your environment.

To add the missing MIME type to your permitted list, see Resolving MIME type errors (document management).

📌Note: Multiple MIME types can be added for a single file extension by appending a number to the extension — for example, pdf1, pdf2. This is useful where the same file type returns different MIME type values.


Validation errors or fields behaving differently

v12.05 introduces tightened validation on a number of fields across modules. If a field that previously accepted a value now returns a validation error, or a field appears masked or restricted when it was not before, work through the following steps.

  1. Note the exact error message and the field or screen where it occurs.

  2. Check the v12.05 Detailed Release Notes for your product area to confirm whether the validation change is intentional. A link to the release notes is available on the Access Coins ERP+ v12.05 Release Announcement.

  3. Check whether a new or changed parameter controls the behaviour. A full list of new and deleted parameters for v12.05 is available from the release announcement.

  4. If the validation is blocking a process you need to complete, raise a support ticket with the field name, the value you are trying to enter and the exact error message.

⚠️Important: Do not attempt to work around a validation error by entering an approximate or dummy value. This can cause data integrity issues that are difficult to reverse. Raise a support ticket instead.


Mobile technicians cannot see visits or submit jobs

After upgrading to v12.05, technicians using the Mobile Tech app may find they cannot see visits or submit existing jobs. This is caused by a missing Agreement Security setting that must be applied post-upgrade.

Apply Agreement Security

  1. Go to Service Management, then Setup, then Company Setup.

  2. Select Security, then Agreement Security.

  3. Add an asterisk (*) to the Security List field to grant access to all technicians.

  4. Use Bulk Update to apply the change to all technicians at once.

  5. Ask technicians to log out of the Mobile Tech app and log back in.

📌Note: v12.05 requires Mobile Tech iOS version 2.14.0 or later. If technicians are running an earlier version, they must update the app before Agreement Security will take effect. For non-hosted environments, M1x v4.5.0.0 is also required.


Function access errors after upgrade

v12.05 includes changes to function security. Some users may find they can no longer access functions they could previously use, or that new functions are not yet visible to their group or role.

  1. Review the function security changes document linked from the Access Coins ERP+ v12.05 Release Announcement — this lists all functions added, changed or removed in this version.

  2. Use the User Function Access tab in System Setup to confirm whether the user has been explicitly denied access or whether their group needs updating.

  3. Grant access at the user or group level as required. See How function access works for step-by-step instructions.

  4. If access was previously working and has been removed by the upgrade, raise a support ticket with the function code and the username affected.


Raise a support ticket

Raise a support ticket if:

  • A display error or blank screen persists after clearing the cache and checking your browser version.

  • A MIME type error cannot be resolved by adding the type to the permitted list.

  • A validation error is blocking a process and you cannot identify the cause in the release notes or parameter list.

  • Technicians still cannot see visits after Agreement Security has been applied and the app has been updated.

  • A function access issue cannot be resolved using the User Function Access tab.

Include your current version number, the module or screen affected, the exact error message and a screenshot where possible. Reference 'v12.05 upgrade' in your ticket subject so it is routed to the correct team.

Did this answer your question?