Start a conversation
  1. ACRM Support
  2. ACRM - Articles
  3. Public Articles

Aurea CRM Web 15.24: Text in “Mini Details” Rows Cannot Be Selected (Fix in 15.25.4)

Contents

Overview

After upgrading to Aurea CRM Web 15.24 (for example, BTBi 15.24.0.3161), users may be unable to highlight/select text inside Mini Details rows in list views (for example, to copy an email address). There is no error message; the UI simply does not allow selecting the text.

This is a front-end/UI regression introduced in 15.24. A permanent fix is scheduled for Aurea CRM 15.25.4, which restores text selection in Mini Details rows.

<supportagent>

Agent Notes

Investigation Summary:

The issue was reproduced across browsers and users and could be reproduced on a standard 15.24 installation. Logs and network traces were reviewed to confirm the backend/API was returning correct values while the UI prevented text selection in Mini Details rows.

Findings:

  • Affected build confirmed: web.log showed CRM Web version BTBi 15.24.0.3161; no backend errors correlated with Mini Details usage.
  • Backend/API healthy: HAR capture showed Mini Details expansion calls (for example, POST /api/expand/get) returned HTTP 200 with expected JSON containing field values (email/phone/etc.).
  • Not permissions/rights: Values were visible (no canRead/canUpdate-style blocking); the problem was specifically selection/highlighting in the UI.
  • Not configuration: FieldControl type MiniDetails had no special attributes restricting selection; no custom JS in configuration explaining selection block.
  • Not browser-specific: Reproduced across browsers.
  • Conclusion: UI/front-end regression/change introduced in CRM Web 15.24 affecting text selection in Mini Details rows.
  • Workarounds attempted (not successful in the affected environment):
    • CSS override attempts to force selection via user-select: text !important in the active theme’s update.css and (if used) update.touchable.css.
    • Theme rebuild/caching steps: delete web\styles\.compiled, recycle IIS app pool / perform IIS reset, clear browser cache / test incognito, and warm up the site to trigger recompilation.
    • Expanded selectors to target list child rows (for example, .u8-grid-table > tbody > tr.child and descendants) in case selection blocking was applied at the row level.
    • DevTools validation: inspect tr.child computed styles and confirm whether user-select is overridden/crossed out.
    • Runtime-block hypothesis: selection blocking potentially applied via inline styles and/or event handling (for example, selectstart), meaning CSS alone may not override.
    • Custom script attempt: load a script/module to neutralize selectstart handling and set user-select at runtime; the script loaded but selection remained blocked.

Escalation: Engineering defect tracked as eng-maintenance issue 15714 (link redacted to <engineering_issue_link>).

Engineering implemented a permanent fix scheduled for Aurea CRM 15.25.4, explicitly restoring text selection in Mini Details rows.

</supportagent>

Solution

Issue

In Aurea CRM Web 15.24 (for example, BTBi 15.24.0.3161), text in Mini Details rows within list views may become unselectable. Users cannot highlight/mark values such as email addresses or phone numbers to copy them. There is no error message; selection simply does not work.

Root cause

This behavior is a UI regression in CRM Web 15.24. The backend continues returning the correct field values; the issue is in the front-end/UI layer.

Permanent fix

The permanent fix is scheduled to be included in Aurea CRM version 15.25.4, which restores text selection in Mini Details rows.

What to do

  1. Plan an upgrade to Aurea CRM 15.25.4 (or later) once it is available in your delivery channel.
  2. After upgrading, clear browser cache (or test in a private/incognito window) to ensure the updated front-end assets are used.

How to verify after upgrading

  1. Open CRM Web and navigate to a list view where Mini Details are used.
  2. Expand/open Mini Details for a record.
  3. Click-drag to highlight an email/phone value inside Mini Details.
  4. Confirm the text highlights and can be copied.

Temporary Workaround

No reliable configuration-level workaround was available for 15.24 in the affected environments. If you must copy values before upgrading, use a view where fields remain selectable (for example, open the full record details view) until 15.25.4 is applied.

Note on CSS/script approaches

CSS or custom-script attempts may be unreliable if the selection block is applied by runtime UI behavior (for example, inline styles and/or event handling such as selectstart).

/* Example of an attempted CSS override (may not work in 15.24 if selection is blocked at runtime) */
.selector-for-mini-details {
  user-select: text !important;
}

When to Contact Support

If Mini Details text selection is still blocked after upgrading to 15.25.4 (or later) and clearing cache, provide the exact CRM Web version/build and clear steps to reproduce.

Frequently Asked Questions

1. How do I know I’m hitting this exact issue?

In CRM Web list views, Mini Details values (email/phone/etc.) are visible but you cannot highlight/mark the text to copy it. There is no error message, and it happens for all users/browsers.

2. Is this caused by permissions or my FieldControl configuration?

If the values display normally but cannot be selected, and it began immediately after upgrading to 15.24, this is consistent with the 15.24 UI regression rather than a rights/configuration issue.

3. What version contains the permanent fix?

The fix is scheduled to ship in Aurea CRM 15.25.4 (or later).

4. What should I check if we upgrade but selection still doesn’t work?

Clear browser cache or test in a private window. If your environment uses cached/compiled front-end assets, ensure the upgraded assets are being served (and not an older cached set). If it persists, provide the upgraded version/build and reproduction steps.

5. Can CSS or custom scripts restore selection in 15.24?

Attempts may not be reliable because the selection block can be applied by runtime UI behavior. If you cannot upgrade immediately, the most reliable workaround is to open the full record details view to copy field values until 15.25.4 is applied.

Choose files or drag and drop files
ai_initiated
atlas_studio
kb_automation
Was this article helpful?
Yes
No

  1. Priyanka Bhotika

  2. Posted

Comments