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: Proper Case for Names

Zoho Deluge: Proper Case for Names

What?
This is an open article without any completion in mind; to set the proper case of a name, as in capitalize the first letter, lower case the rest but then with exceptions.

Why?
Some of the Zoho Apps are incredibly case-sensitive and consider some records containing people's names as duplicates, when actually they are the same entity but may have uppercased a letter in their name while the other entry does not...

This article is a start and adaptation of my previous article Convert to Proper Case in T-SQL which I had previously used for the migration of a HR system. This is intended to work using Zoho Deluge.

How?
There are a number of combinations that I won't have thought of but the below code sufficed for my current task, common English and some European names:

copyraw
//
// set first and last name
v_FirstName = "BILLIE-JO";
v_LastName = "MCDONALD-O'LEARY ii OF CAMBRIDGE-worcester-OXFORD";
//
// let's deal with double or triple barrelled first names
v_FirstName = v_FirstName.replaceAll("-", " :|JOEL|: ", true).proper();
v_FirstName = v_FirstName.replaceAll(" :|joel|: ", "-", true);
//
// Names starting with Mc, O', D', I'
l_ExceptionPrefixes = {"Mc", "O'", "D'", "I'"};
//
// deal with double barrelled surnames
l_FormattedLastName = List();
l_LastNameParts = v_LastName.toList("-");
for each v_LastNamePart in l_LastNameParts
{
	//
	// default to proper
	v_LastNamePart = v_LastNamePart.proper();
	//
	// if exception prefixes
	for each v_Prefix in l_ExceptionPrefixes
	{
		if(v_LastNamePart.indexOf(v_Prefix)==0)
		{
			v_LastNamePart = v_LastNamePart.replaceFirst(v_Prefix,v_Prefix + " :|JOEL|: ", true).proper();
			v_LastNamePart = v_LastNamePart.replaceAll(" :|joel|: ", "", true);
		}
	}
	//
	// add back to our hyphen separated list
	l_FormattedLastName.add(v_LastNamePart);
}
v_LastName = l_FormattedLastName.toString("-") + " ";
//
// affix exceptions
l_Exceptions = {" II", " III", " the ", " de ", " of ", " van ", " and "};
for each v_Exception in l_Exceptions
{
	v_LastName = v_LastName.replaceAllIgnoreCase(v_Exception, v_Exception, false);
}
v_LastName = v_LastName.trim();
//
// join all together
v_FullName = trim(v_FirstName + " " + v_LastName);
info v_FullName;
//
// yields: Billie-Jo McDonald-O'Leary II of Cambridge-Worcester-Oxford
  1.  // 
  2.  // set first and last name 
  3.  v_FirstName = "BILLIE-JO"
  4.  v_LastName = "MCDONALD-O'LEARY ii OF CAMBRIDGE-worcester-OXFORD"
  5.  // 
  6.  // let's deal with double or triple barrelled first names 
  7.  v_FirstName = v_FirstName.replaceAll("-", :|JOEL|: ", true).proper()
  8.  v_FirstName = v_FirstName.replaceAll(:|joel|: ", "-", true)
  9.  // 
  10.  // Names starting with Mc, O', D', I' 
  11.  l_ExceptionPrefixes = {"Mc", "O'", "D'", "I'"}
  12.  // 
  13.  // deal with double barrelled surnames 
  14.  l_FormattedLastName = List()
  15.  l_LastNameParts = v_LastName.toList("-")
  16.  for each v_LastNamePart in l_LastNameParts 
  17.  { 
  18.      // 
  19.      // default to proper 
  20.      v_LastNamePart = v_LastNamePart.proper()
  21.      // 
  22.      // if exception prefixes 
  23.      for each v_Prefix in l_ExceptionPrefixes 
  24.      { 
  25.          if(v_LastNamePart.indexOf(v_Prefix)==0) 
  26.          { 
  27.              v_LastNamePart = v_LastNamePart.replaceFirst(v_Prefix,v_Prefix + :|JOEL|: ", true).proper()
  28.              v_LastNamePart = v_LastNamePart.replaceAll(:|joel|: ", "", true)
  29.          } 
  30.      } 
  31.      // 
  32.      // add back to our hyphen separated list 
  33.      l_FormattedLastName.add(v_LastNamePart)
  34.  } 
  35.  v_LastName = l_FormattedLastName.toString("-") + " "
  36.  // 
  37.  // affix exceptions 
  38.  l_Exceptions = {" II", " III", " the ", " de ", " of ", " van ", " and "}
  39.  for each v_Exception in l_Exceptions 
  40.  { 
  41.      v_LastName = v_LastName.replaceAllIgnoreCase(v_Exception, v_Exception, false)
  42.  } 
  43.  v_LastName = v_LastName.trim()
  44.  // 
  45.  // join all together 
  46.  v_FullName = trim(v_FirstName + " " + v_LastName)
  47.  info v_FullName; 
  48.  // 
  49.  // yields: Billie-Jo McDonald-O'Leary II of Cambridge-Worcester-Oxford 

Caveat(s):
  • This solution does not cater for the Mac prefix; because "Mackayla", "Macie", "Maci", "Macala", "Mack", "Macoy", "Macey", "Macedonia"...

Source(s):
Category: Zoho Deluge :: Article: 384

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