Normalize text formatting in Excel

Auteur: AILesson6 min de préparationTesté avec:ChatGPTRévisé: 2026-08-28

Réponse rapide

Standardize presentation differences without changing identifiers or meaningful text. Fournir: Fields and meanings, Representative values, Approved display standard. Résultat attendu: Field-specific normalization formulas, exception flags, and before-after tests.

1

Ajouter votre contexte

Votre texte reste dans ce navigateur. AILesson Prompts ne l’envoie ni à un modèle ni à un serveur.

2

Votre prompt

Les champs non remplis restent visibles sous forme d’espaces réservés, afin que vous puissiez quand même copier et modifier le prompt.

Design field-specific Excel rules to normalize text formatting.

Fields and meanings:
[fields]

Representative values:
[samples]

Approved display standard:
[standard]

Separate harmless presentation cleanup from transformations that could change identity or meaning. Do not apply PROPER, remove punctuation, or convert text to numbers across every field. Preserve raw values and return one rule or formula per field, an exception condition, and before/after examples. Test nonbreaking spaces, repeated internal spaces, apostrophes, hyphens, acronyms, multilingual text, blanks, and identifiers with leading zeros.
Essayer dans le Playground
Privé par défautL’assemblage du prompt se fait localement dans votre navigateur. Évitez de placer des informations confidentielles dans un service d’IA, sauf si votre organisation l’autorise.

De l'entrée au résultat

Un exemple détaillé

Voyez comment un contexte concret transforme cette recette en résultat utilisable.

Entrée réelle

Fields and meanings
A CustomerCode is a text identifier where leading zeros matter; B Email is case-insensitive for our matching; C ContactName is human-entered multilingual text; D Status is a controlled label.
Representative values
A: 001-AB, ' 001-AB '; B: ANA@EXAMPLE.COM, ana@example.com plus nonbreaking spaces; C: o'connor, ANA PÉREZ, 王 小明; D: in progress, In Progress, IN-PROGRESS.
Approved display standard
CustomerCode: trim outer whitespace only. Email: trim and lowercase. ContactName: remove outer and repeated spaces but do not force case. Status: canonical value 'In progress' after an approved mapping.

Exemple de sortie

Keep the four raw columns and create clean companions. Replace nonbreaking spaces with ordinary spaces before trimming.

  • CustomerCode: =TRIM(SUBSTITUTE(A2,CHAR(160)," ")). Do not VALUE-convert or remove the hyphen; 001-AB must remain text. Flag any internal spaces.
  • Email: =LOWER(TRIM(SUBSTITUTE(B2,CHAR(160)," "))). Flag values that contain internal spaces or lack a usable @ structure; do not invent a corrected address.
  • ContactName: Microsoft 365: =TEXTJOIN(" ",TRUE,TEXTSPLIT(TRIM(SUBSTITUTE(C2,CHAR(160)," "))," ",,TRUE)). This collapses repeated spaces but deliberately preserves o'connor, ANA PÉREZ, and Chinese characters as entered. Do not use PROPER without human approval.
  • Status: normalize a comparison key with lowercase, trimmed spaces, and an approved hyphen-to-space rule, then XLOOKUP that key in a two-column mapping table. Unmapped values return Review.

Tests confirm that the customer code keeps both zeros, the two email variants normalize equally, names retain punctuation and case, and the three approved status variants map to In progress. Store RuleApplied and ReviewReason next to every clean value.

Pourquoi cela fonctionne

  1. 1

    Field-specific rules prevent a visual cleanup from corrupting IDs, acronyms, or names.

  2. 2

    Raw and clean columns reveal every transformation instead of overwriting evidence.

Vérifier le résultat

  • Has each field been classified as free text, controlled label, or identifier?

  • Are leading zeros and meaningful punctuation preserved?

  • Can changed values be compared directly with their raw source?

Utilisez-la en toute confiance

Questions fréquentes

Des réponses pratiques sur le bon moment pour utiliser cette recette, ce qu’il faut fournir et les cas où une vérification humaine reste nécessaire.

What should I prepare before using “Normalize text formatting in Excel”?

For “Normalize text formatting in Excel,” prepare Fields and meanings, Representative values, and Approved display standard. Replace placeholders only with information you can verify. If a detail is unknown, preserve that uncertainty explicitly instead of asking the model to infer it.

When is the “Normalize text formatting in Excel” result not ready to use?

The result is not ready if it does not yet deliver the stated outcome—Field-specific normalization formulas, exception flags, and before-after tests—from the supplied evidence, or if it relies on unresolved assumptions, missing approvals, or invented details. Use the checks as release gates: revise the source inputs or assign a named, authorized reviewer instead of polishing an unsupported output.

Which AI tools have recorded tests for “Normalize text formatting in Excel”?

The published test record for “Normalize text formatting in Excel” lists ChatGPT as of 2026-08-28. This confirms recorded runs, not guaranteed compatibility or identical results in later product versions. For another tool or version, keep every constraint visible and repeat the result checks before use.

Plus de façons d'explorer

Où se situe cette recette

Faites avancer votre travail