Share all details about your problem, including any error messages you may have received.
Recently, I got a usecase to modify the resourceObject for a Database Application. I want to understand what should be the better approach while using the rules.
Like which rules can be used and which type of rule will be better.
You can use Customization Rule or BUildMap rule if the connector Type is JDBC.
But in case of this JDBC Connector, Build Map rule will be better because Customization Rule is more expensive to run during aggregation.
The Reason why it is expensive is below:
The BuildMap Rule executes once per record at the raw data level — it just manipulates a simple Map before IIQ object creation, which is lightweight.
The Customization Rule runs after the object is built (Account or Identity), meaning IIQ has already created and loaded full objects into memory, making it heavier on processing and memory usage.
Therefore, BuildMap is faster and more efficient for transformations during aggregation.
@Jadhikary if the new attribute is based on other columns, you can also consider modify your query or stored procedure to return the additional column as a query result, then you don’t need any buildmap or customization rule. In case, this is something not achievable via query, go with build map rule as explained above.
Note: Found a fix?Help the community by marking the comment as solution. Feel free to react(,, etc.)with an emoji to show your appreciation or message me directly if your problem requires a deeper dive.