Audit Excel headers, field definitions, and data types

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

Réponse rapide

Compare a workbook with its intended schema before import, analysis, or automation. Fournir: Workbook purpose and consumer, Expected schema, Observed headers and sample values. Résultat attendu: A schema dictionary, conformance report, and row-level validation plan.

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.

Audit an Excel workbook against its intended schema.

Purpose and downstream consumer:
[purpose]

Expected schema:
[expected]

Observed headers and representative values:
[observed]

Check header names, order only when order matters, missing and unexpected fields, data types, date and number storage, requiredness, uniqueness, allowed values, and cross-field rules. Distinguish cell formatting from underlying value type. Return a data dictionary, schema-difference table with severity, row-level validation formulas, blocking issues, and an acceptance checklist. Do not declare conformance from display appearance alone.
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

Workbook purpose and consumer
Upload weekly orders to an operations system. Column order is irrelevant, but exact header names and field types are required.
Expected schema
OrderID required unique text; OrderDate required Excel date; CustomerID required text; Amount required number >=0; Currency required one of USD, EUR, GBP; Cancelled optional TRUE/FALSE. No extra fields containing notes may be uploaded.
Observed headers and sample values
Headers: Order ID, OrderDate, CustomerID, Amount, Currency, Cancelled, InternalNotes. Samples include Order ID 00125; OrderDate displayed 08/27/2026 but imported as text in some rows; Amount '$1,240.00' stored as text; Currency usd; Cancelled Yes.

Exemple de sortie

Schema differences

IssueSeverityEvidenceRequired action
Order ID header differs from OrderIDBlockingobserved spacerename exactly
InternalNotes is unexpectedBlocking/privacyextra sensitive-capable fieldexclude from upload
OrderDate mixed typeBlockingsome values are textconvert and validate, do not only reformat
Amount stored as currency textBlocking$ and comma in textparse under confirmed locale, retain raw
Currency uses lowercaseFixableusdmap approved case to USD
Cancelled uses YesBlocking until mappedcontract requires Booleanapprove Yes/No mapping or reject

Create a data dictionary with field, definition, stored type, required, allowed values, example, and validation. Row checks can include =AND(ISTEXT([@OrderID]),[@OrderID]<>""), =ISNUMBER([@OrderDate]), =AND(ISNUMBER([@Amount]),[@Amount]>=0), =ISNUMBER(XMATCH([@Currency],{"USD","EUR","GBP"})), and =OR([@Cancelled]=TRUE,[@Cancelled]=FALSE,[@Cancelled]=""). Check uniqueness with COUNTIF. Accept only when exact required headers exist, InternalNotes is excluded, every row passes type and domain checks, OrderID count equals unique OrderID count, and rejected rows are listed separately. Preserve 00125 as text.

Pourquoi cela fonctionne

  1. 1

    A schema contract catches structural failures before they become misleading analysis results.

  2. 2

    Testing underlying value types reveals dates and numbers that only look correctly formatted.

Vérifier le résultat

  • Are required fields, keys, and allowed values explicitly documented?

  • Do validation checks inspect stored types rather than display formats?

  • Are blocking import failures separated from nonblocking presentation differences?

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 “Audit Excel headers, field definitions, and data types”?

For “Audit Excel headers, field definitions, and data types,” prepare Workbook purpose and consumer, Expected schema, and Observed headers and sample values. 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 “Audit Excel headers, field definitions, and data types” result not ready to use?

The result is not ready if it does not yet deliver the stated outcome—A schema dictionary, conformance report, and row-level validation plan—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 “Audit Excel headers, field definitions, and data types”?

The published test record for “Audit Excel headers, field definitions, and data types” 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