Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
A backslash is seen whenever there is an apostrophe in the text of a hint message on a read only price field - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • A backslash is seen whenever there is an apostrophe in the text of a hint message on a read only price field
KB0751614

A backslash is seen whenever there is an apostrophe in the text of a hint message on a read only price field


366 Views Last updated : Apr 7, 2024 public Copy Permalink
KB Summary by Now Assist

Issue

A backslash is seen whenever there is an apostrophe in the text of a hint message on a read only price field

 

Release

Jakarta, Kingston

Cause

This seems to occur on price field or a field that has a special character like $ and this is not properly escaping hence causing the backslash to follow an apostrophe.

Steps to reproduce:

  1. Go to sc_cat_item.list
  2. Find Apple Watch
  3. Right click on Price and Click Configure Dictionary and set it to Read only and update the record
  4. Right click and Configure Label
  5. In hint type "That's all folks" and update the record
  6. Hover over the price and you will see the \ will show next to the apostrophe

I did test this in London, Madrid and New York, and I was unable to reproduce the problem in those versions

Resolution

This issue is fixed in London and forward so using those versions would be the first recommendation. If you require a workaround, you can create a UI policy that makes the field read only which will prevent the issue from happening. The issue is only triggered if the dictionary record is set to read only.


The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.