For Zoho services only


I'm currently part of a wider delivery team at Ascent Business Solutions, recognised as a leading Zoho Premium Solutions Partner in the United Kingdom.

Ascent Business Solutions support organisations with everything from targeted technical fixes through to full Zoho CRM implementations and long-term platform adoption. Working as a team rather than a one-person consultancy allows projects to move forward consistently, with access to the right skills at each stage.

The team I manage specialises in API integrations between Zoho and third-party finance and commerce platforms such as Xero, Shopify, WooCommerce, and eBay. Much of our work involves solving integration challenges that fall outside standard documentation, supporting new ideas, new sectors, and evolving business models.

Success is measured through practical outcomes and return on investment, ranging from scaling small operations into high-turnover businesses to delivering rapid gains through online payments, automation, and streamlined digital workflows.

If you are looking for structured Zoho expertise backed by an established consultancy, you can contact Ascent Business Solutions on 0121 392 8140 (UK), email info@ascentbusiness.co.uk, or visit https://www.ascentbusiness.co.uk.
Zoho Deluge: Regex Rounding and/or Removing Trailing Zeros

Zoho Deluge: Regex Rounding and/or Removing Trailing Zeros

What?
A very quick article on a cool snippet of code, another regular expression, I've been trying out to round up a number or at least to remove the trailing zeros. I could have added this to my Zoho Deluge - Some Useful Regular Expressions list but I felt this deserved its own article.

Why?
A client wanted the discount displayed on a template and if they gave 10% discount, it would display as 10.00%. And they need the decimal because sometimes they might offer 12.5%. But when it displays in a template, it isn't that pretty to look at: Instead, could they have 10% to display instead of 10.00%, and display 12.5% instead of 12.50%.

Well there might be a longer solution without using a regular expression (regex), as in check for the decimal point, check each digit thereafter to see if there are zeros... But I'm keen on avoiding using loops where possible so we don't breach a statement execution limit in the Zoho app function.

How?
If we're not going to use loops, then the next best thing I'm aware of is a regular expression.

So the first expression I came up with worked to a certain point but didn't round up the numbers, in other words, it didn't remove the unnecessary zeros. Note that in the following regex, and if using Zoho Creator, you need to replace the double-backslash with a single backslash:
copyraw
v_Test1 = 12.300;
info v_Test1.toString().replaceAll("(\\.\\d*?[1-9])0+$", "$1", false);
// yields 12.3

// same expression again but with a different value
v_Test2 = 12.000;
info v_Test2.toString().replaceAll("(\\.\\d*?[1-9])0+$", "$1", false);
// yields 12.000
  1.  v_Test1 = 12.300
  2.  info v_Test1.toString().replaceAll("(\\.\\d*?[1-9])0+$", "$1", false)
  3.  // yields 12.3 
  4.   
  5.  // same expression again but with a different value 
  6.  v_Test2 = 12.000
  7.  info v_Test2.toString().replaceAll("(\\.\\d*?[1-9])0+$", "$1", false)
  8.  // yields 12.000 

So this isn't quite right, so let's get a regex that rounds numbers up but pays attention to where the decimal point is:
copyraw
v_Test3 = 12.000;
info v_Test3.toString().replaceAll("^(^-?\\d+\\.\\d*[1-9])(0+$)|(\\.0+$)", "$1", false);
// yields 12

v_Test4 = 12.300;
info v_Test4.toString().replaceAll("^(^-?\\d+\\.\\d*[1-9])(0+$)|(\\.0+$)", "$1", false);
// yields 12.3

v_Test5 = 12.345;
info v_Test5.toString().replaceAll("^(^-?\\d+\\.\\d*[1-9])(0+$)|(\\.0+$)", "$1", false);
// yields 12.345

v_Test6 = 120.000;
info v_Test6.toString().replaceAll("^(^-?\\d+\\.\\d*[1-9])(0+$)|(\\.0+$)", "$1", false);
// yields 120

v_Test7 = -123.4567;
info v_Test7.toString().replaceAll("^(^-?\\d+\\.\\d*[1-9])(0+$)|(\\.0+$)", "$1", false);
// yields -123.4567
  1.  v_Test3 = 12.000
  2.  info v_Test3.toString().replaceAll("^(^-?\\d+\\.\\d*[1-9])(0+$)|(\\.0+$)", "$1", false)
  3.  // yields 12 
  4.   
  5.  v_Test4 = 12.300
  6.  info v_Test4.toString().replaceAll("^(^-?\\d+\\.\\d*[1-9])(0+$)|(\\.0+$)", "$1", false)
  7.  // yields 12.3 
  8.   
  9.  v_Test5 = 12.345
  10.  info v_Test5.toString().replaceAll("^(^-?\\d+\\.\\d*[1-9])(0+$)|(\\.0+$)", "$1", false)
  11.  // yields 12.345 
  12.   
  13.  v_Test6 = 120.000
  14.  info v_Test6.toString().replaceAll("^(^-?\\d+\\.\\d*[1-9])(0+$)|(\\.0+$)", "$1", false)
  15.  // yields 120 
  16.   
  17.  v_Test7 = -123.4567
  18.  info v_Test7.toString().replaceAll("^(^-?\\d+\\.\\d*[1-9])(0+$)|(\\.0+$)", "$1", false)
  19.  // yields -123.4567 

Awesome!

Recap on the CRM and Creator version:
copyraw
v_Test8 = 12.000;
info v_Test8.toString().replaceAll("^(^-?\d+\.\d*[1-9])(0+$)|(\.0+$)", "$1", false);
// yields 12
  1.  v_Test8 = 12.000
  2.  info v_Test8.toString().replaceAll("^(^-?\d+\.\d*[1-9])(0+$)|(\.0+$)", "$1", false)
  3.  // yields 12 

Additional Note(s):
You might ask why not use the built-in round() function? Well I admit that round() needs to be used for currencies. The issue is that round() only rounds up decimals to integers when the datatype is an integer and not a decimal:
copyraw
// syntax:
// v_Test9.round(2);
// round(v_Test9, 2);

v_Test9 = 10.0;
info v_Test9.round(2);
// yields 10.00

v_Test10 = 10;
info v_Test10.round(2);
// yields 10

v_Test11 = 10.1;
info v_Test11.round(2);
// yields 10.10
  1.  // syntax: 
  2.  // v_Test9.round(2)
  3.  // round(v_Test9, 2)
  4.   
  5.  v_Test9 = 10.0
  6.  info v_Test9.round(2)
  7.  // yields 10.00 
  8.   
  9.  v_Test10 = 10
  10.  info v_Test10.round(2)
  11.  // yields 10 
  12.   
  13.  v_Test11 = 10.1
  14.  info v_Test11.round(2)
  15.  // yields 10.10 

However the opposite can be done as long as you set the datatype to a decimal first and then use the rounding. In other words the following will force the number to have 2 decimal places:
copyraw
v_Test1 = 12; 
info v_Test1.toDecimal().round(2);
// yields 12.00 

v_Test2 = 12.0; 
info v_Test2.toDecimal().round(2);
// yields 12.00 
 
v_Test3 = 12.000; 
info v_Test3.toDecimal().round(2); 
// yields 12.00 
  
v_Test4 = 12.300; 
info v_Test4.toDecimal().round(2);
// yields 12.30 
  
v_Test5 = 12.345; 
info v_Test5.toDecimal().round(2);
// yields 12.35 
  
v_Test6 = 120.000; 
info v_Test6.toDecimal().round(2);
// yields 120.00 
  
v_Test7 = -123.4567; 
info v_Test7.toDecimal().round(2);
// yields -123.46
  1.  v_Test1 = 12
  2.  info v_Test1.toDecimal().round(2)
  3.  // yields 12.00 
  4.   
  5.  v_Test2 = 12.0
  6.  info v_Test2.toDecimal().round(2)
  7.  // yields 12.00 
  8.   
  9.  v_Test3 = 12.000
  10.  info v_Test3.toDecimal().round(2)
  11.  // yields 12.00 
  12.   
  13.  v_Test4 = 12.300
  14.  info v_Test4.toDecimal().round(2)
  15.  // yields 12.30 
  16.   
  17.  v_Test5 = 12.345
  18.  info v_Test5.toDecimal().round(2)
  19.  // yields 12.35 
  20.   
  21.  v_Test6 = 120.000
  22.  info v_Test6.toDecimal().round(2)
  23.  // yields 120.00 
  24.   
  25.  v_Test7 = -123.4567
  26.  info v_Test7.toDecimal().round(2)
  27.  // yields -123.46 
Source(s):
Category: Zoho Deluge :: Article: 338

Joes Word Cloud

Accreditation

Badge - Zoho Creator Certified Developer Associate
Badge - Zoho Deluge Certified Developer
Badge - Certified Zoho CRM Developer

Donate & Support

If you like my content, and would like to support this sharing site, feel free to donate using a method below:

Paypal:
Donate to Joel Lipman via PayPal

Bitcoin:
Donate to Joel Lipman with Bitcoin bc1qf6elrdxc968h0k673l2djc9wrpazhqtxw8qqp4

Ethereum:
Donate to Joel Lipman with Ethereum 0xb038962F3809b425D661EF5D22294Cf45E02FebF

Credit where Credit is Due:


Feel free to copy, redistribute and share this information. All that we ask is that you attribute credit and possibly even a link back to this website as it really helps in our search engine rankings.

Disclaimer: Please note that the information provided on this website is intended for informational purposes only and does not represent a warranty. The opinions expressed are those of the author only. We recommend testing any solutions in a development environment before implementing them in production. The articles are based on our good faith efforts and were current at the time of writing, reflecting our practical experience in a commercial setting.

Thank you for visiting and, as always, we hope this website was of some use to you!

Kind Regards,

Joel Lipman
www.joellipman.com