Static Lookup
Infoveave Data Automation — JSON & Array
Your Grade column has A, B, C, D values. Your report needs Excellent, Good, Average, Poor. Configure the mapping once — it applies to every row on every pipeline run.
Business data frequently uses coded values, abbreviations, or numeric grades that need to be translated into human-readable labels for reporting, classification, and downstream analysis. A Grade column with A/B/C/D codes needs Excellent/Good/Average/Poor labels. A Score column with numeric values needs High/Medium/Low performance bands. A Status column with numeric codes needs descriptive text labels. Performing these translations requires VLOOKUP or IFS in Excel, CASE WHEN in SQL, or a dictionary map and .map() in Python — all of which must be updated whenever the mapping rules change. Static Lookup centralizes the entire mapping configuration in a single pipeline step with a visual lookup table editor, supporting both exact key-value matching and numeric range-based banding. Changes to mappings require no code edits — only the lookup table configuration is updated.
What Static Lookup does
Replace or annotate column values with mapped labels using a configured key-value dictionary or numeric range rules in Infoveave. Convert grade codes to descriptions, score ranges to performance bands, category codes to display labels, and status codes to readable text — without VLOOKUP, CASE WHEN, or dictionary-based Python mapping code.
When to use Static Lookup
- You have a column with categorical codes, abbreviations, or single-letter grades that need to be translated to human-readable labels for reporting, export, or dashboard display — such as converting status codes to descriptions or grade letters to performance labels
- You have a numeric score, quantity, age, or metric column that needs to be classified into performance bands, risk tiers, age groups, or size categories based on defined numeric ranges — such as classifying NPS scores into Promoter, Passive, and Detractor bands
- You are preparing data for a report where business stakeholders expect readable category labels rather than system codes, and maintaining the translation logic in a pipeline step allows the mapping to be updated by a business analyst without code changes
- You are building a scoring or classification pipeline where model output scores need to be converted to action labels — such as converting a probability score to a High/Medium/Low risk classification based on defined threshold ranges
When to avoid it
- Your lookup table is large (hundreds or thousands of rows) or changes frequently — for large dynamic lookup tables, use a join-based approach with a lookup reference dataset rather than a static in-step configuration
- You need to look up values from a separate external table or file rather than a fixed configured mapping — use a dataset join or enrichment step that can reference an external data source
- The mapping requires conditional logic based on multiple columns simultaneously — Static Lookup maps one column at a time; for multi-column conditional logic, use a formula or expression step
Where it fits in your Infoveave automation
Static Lookup is one step inside a multi-step Infoveave workflow. Chain it with other activities — no code, no manual hand-offs.
Build this workflow visually in Infoveave Data Automation — drag, connect, and schedule with no infrastructure setup.
How teams use Static Lookup
Real scenarios where this transformation saves hours of manual work.
Convert Customer Tier Codes to Display Labels for Loyalty Reporting
A retail loyalty team maintains customer records with a TierCode column containing system codes (T1, T2, T3, T4) that map to Platinum, Gold, Silver, Bronze labels in reports and email communications. Static Lookup is configured with a key-value map (T1→Platinum, T2→Gold, T3→Silver, T4→Bronze) and set to create a new TierLabel column alongside TierCode, so both the system code for processing and the display label for reporting are available in the dataset.
Classify OEE Scores into Performance Bands for Factory Dashboard
A manufacturing analytics team calculates OEE scores per production line. The dashboard requires performance bands — World Class (85-100), Good (70-84), Average (50-69), Poor (below 50) — for traffic-light visualization. Static Lookup is configured with Range Lookup mode, defining four score ranges mapped to the four performance labels. The resulting PerformanceBand column drives the dashboard color coding without requiring any SQL CASE WHEN logic.
Map NPS Response Scores to Promoter Passive Detractor Classification
A bank's customer experience team processes NPS survey responses where each record has a Score column with values 0-10. Responses 9-10 are Promoters, 7-8 are Passives, and 0-6 are Detractors. Static Lookup with Range Lookup mode defines three ranges with the NPS classification labels. The NPSCategory column produced by the lookup is used for segment-level satisfaction analysis and executive reporting.
See Static Lookup in action
Input data (left) is transformed using the configuration below. The output table (right) is ready for dashboards or downstream steps.
GradeYesPerformanceLabelYesNoA → Excellent, B → Good, C → Average, D → PoorInput Data
| StudentID | Grade | Score |
|---|---|---|
| S001 | A | 92 |
| S002 | B | 75 |
| S003 | C | 63 |
| S004 | A | 95 |
| S005 | D | 41 |
Output Data
| StudentID | Grade | Score | PerformanceLabel |
|---|---|---|---|
| S001 | A | 92 | Excellent |
| S002 | B | 75 | Good |
| S003 | C | 63 | Average |
| S004 | A | 95 | Excellent |
| S005 | D | 41 | Poor |
Configuration
Key fields to configure in the Infoveave workflow builder. Full reference available in the documentation.
Column
Select the column whose values will be looked up against the configured mapping. For key-value mode, values are matched exactly (case-sensitive) against the lookup keys. For range mode, values are compared numerically against the defined range boundaries.
Create New Column
When enabled, the mapped label is written to a new column whose name is set in New Column Name, leaving the original source column unchanged. When disabled, the mapped label replaces the original value in the source column itself — use this when the code is no longer needed and only the label matters downstream.
Use Range Lookup
When disabled, the transformation performs exact key matching using the configured Lookup Map dictionary — best for categorical codes and grade letters. When enabled, the transformation uses the Range Lookup Items configuration where each rule defines a Start value, End value, and the Label to assign when a row's value falls within that range.
Lookup Map (key-value mode)
Define the mapping as a list of key-value pairs. Each key is the exact value to match in the source column. The corresponding value is the label to assign. Keys not found in the mapping produce null in the output for that row.
Range Lookup Items (range mode)
Define the mapping as a list of range rules, each with a Start value, End value (inclusive), and the Label to assign when a row's value falls within that range. Ranges should not overlap. Rows whose values do not fall within any defined range produce null in the output.
Frequently asked questions
Everything you need to know about Static Lookup in Infoveave.
Also in JSON & Array — and what runs before & after
Transformations in the same family as Static Lookup, often chained together in the same Infoveave workflow.
Part of Infoveave Data Automation
80+ transformations. Zero manual steps.
Static Lookup is one of over 80 transformation activities available inside Infoveave workflows. Chain transformations together — no code, no exports, no waiting for IT.
Ready to see Infoveave in action?
