back to top

Removing the Comma (or Changing the Format Pattern) in the Numeric Control in Infor CRM Web

The Numeric control used in QuickForms in the Infor CRM Web client is rendered as a Dojo Dijit at runtime. The properties editor in Application Architect does expose a few properties you can set to change how the numeric value is formatted, such as decimal places, etc. However, it doesn’t allow you to specify a format or pattern for the numeric value. By default, it will always show a comma. This is less than ideal for some numeric values, for example, if your numeric value is a year – or any other value where you just don’t want a comma. The Dojo NumericTextBox does allow for a pattern to be specified, this just isn’t exposed in the control in Application Architect. However, we can modify this at runtime.

To remove the comma from numeric value by first getting a reference to the widget itself and then setting the pattern. If we set the pattern to “#” this will just display the numeric value without any extra formatting. The widget that gets created at runtime isn’t just the Numeric control’s ClientID. We must append “_NumericTextbox_NumberTextBox” to the end of it to get the correct widget. For example, if the Numeric control’s ID is “StartYear”, our widget name will be StartYear.ClientID + “_NumericTextbox_NumberTextBox”. Once we get a reference to the widget, we can change it’s pattern. Finally, to trigger the change in the displayed value, we can trigger it’s blur event handler which will update what is displayed in the control based on the new pattern.

The code to remove the comma would look like this. Add the following to a Load Action:

// javascript code to get control, change pattern, and trigger blur
var script = @"dojo.ready(function() {{
                   var d = dijit.byId('{0}_NumericTextbox_NumberTextBox');
                   d.constraints.pattern = '#';
                   d._onBlur();
               }});";

// inject code on page, change StartYear to the name of your numeric control
ScriptManager.RegisterStartupScript(this, GetType(), "numericFormatScript", string.Format(script, StartYear.ClientID), true);

Now, there will no longer be a comma added to the numeric value and the control will still only allow numeric values as normal. Of course, it would be nice if Infor would add an exposed property for the format in the control in Application Architect, then none of this would be necessary. At least for now, you can manipulate it, if needed, at runtime.

Contact Customer FX for your CRM project
We let our expertise speak for itself - let us know how our all-star team can help on your CRM project
About the Author
Ryan Farley
Ryan Farleyhttps://customerfx.com/article/author/ryanfarley/
Ryan Farley is the Director of Development for Customer FX and creator of slxdeveloper.com. He's been blogging regularly about SalesLogix, now Infor CRM, since 2001 and believes in sharing with the community. His new passion for CRM is Creatio, formerly bpm'online. He loves C#, Javascript, web development, open source, and Linux. He also loves his hobby as an amateur filmmaker.

3 COMMENTS

  1. Hi Ryan, thank you for this post.
    Unfortunately, this doesn’t quite work for me.
    As soon as I change the record or change the value of that field, the comma will be displayed again until I reload the page with F5.

    We are also concerned with a year field. Do you also have a solution to suppress the 0 at NULL values?

    Thank you and best regards

    • Hi Andre, only thing I can think of is that it’s not finding the control, or it’s running before dojo has done it’s work, or that some other error is happening. Any errors in the dev tools console?

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Infor CRM Sync for Exchange: Action Required by August 31, 2026

Using Infor CRM Sync for Exchange with Microsoft 365? Your Exchange administrator must update tenant settings by August 31, 2026 to prevent sync disruption.

[Webinar] What’s Coming Next for Infor CRM SLX and Why v10 Matters

See what’s coming next for Infor CRM SLX, including new marketing workflows, automation improvements, and reasons to consider upgrading to v10.

Disable Caching in Infor CRM SLX Web Client

In the rare case caching is causing issues in the Infor CRM SLX web client, it is possible to disable specific types of caching by making edits using Application Architect, and then deploying.

Exploring AI Options for Infor CRM v10

I've started taking a closer look at the AI capabilities built into Infor CRM v10. Over the next several posts, I'll share what I learn. From the built-in features and supported AI providers to implementation considerations, costs, and practical use cases.

Infor CRM SLX 10.0: Delegate Ownership Changes for “Everyone” Records

Learn how the new EveryoneOwnerAssignment secured action in Infor CRM SLX 10.0 allows designated users to change ownership of Everyone-owned records without requiring Administrator access.

Related Articles

Infor CRM Sync for Exchange: Action Required by August 31, 2026

Using Infor CRM Sync for Exchange with Microsoft 365? Your Exchange administrator must update tenant settings by August 31, 2026 to prevent sync disruption.

[Webinar] What’s Coming Next for Infor CRM SLX and Why v10 Matters

See what’s coming next for Infor CRM SLX, including new marketing workflows, automation improvements, and reasons to consider upgrading to v10.

Disable Caching in Infor CRM SLX Web Client

In the rare case caching is causing issues in the Infor CRM SLX web client, it is possible to disable specific types of caching by making edits using Application Architect, and then deploying.

Exploring AI Options for Infor CRM v10

I've started taking a closer look at the AI capabilities built into Infor CRM v10. Over the next several posts, I'll share what I learn. From the built-in features and supported AI providers to implementation considerations, costs, and practical use cases.

Related Videos