BuildMap rule
Quick answer
The BuildMap rule: shaping each raw record from a delimited or JDBC source into an account map during aggregation.
Key takeaways
- Runs once per raw record from delimited/JDBC sources
- Receives the raw record, returns an attribute Map
- Use it to clean, combine and derive source attributes
- Keep it fast: it runs for every row
When BuildMap runs
A BuildMap rule runs once per raw record read from a delimited file or JDBC source during aggregation, before the data becomes a ResourceObject. It builds the map of attribute names to values.
Inputs and return
You get the raw record (cols and record) and return a Map. This is where you clean, combine or compute source attributes before correlation.
Typical uses
Trimming whitespace, concatenating name fields, decoding status codes, and deriving an account identifier that later correlation relies on.
Keep it light
BuildMap runs for every row, so keep logic fast and avoid per-row queries against IdentityIQ.
Want to learn this properly?
Our live, instructor-led SailPoint Training covers this hands-on, with real projects and a certification path.
Check your understanding
How often does a BuildMap rule run?
- A. Once per aggregation
- B. Once per raw record
- C. Once per identity
- D. Once per approval
Show answer
B. Once per raw record
BuildMap runs once for every raw record read from the source.