Portlet Factory, Version 6.1.2

---

 

Using override builders

The SQL Call builder leverages many of the low-level SQL builders during its generation phase. These "internal" SQL builders are configured by SQL Call to use input values that are appropriate for the majority of users. However, there may be scenarios where a user needs to apply a fine grain of control over how these "internal" builders function at runtime. To make this fine grain of control possible the SQL Call builder allows the user to override the "internal" SQL DataSource, SQL Statement, and/or SQL Transform builders used by SQL Call during generation.

Under the group heading "Builder Override Definition" there are three inputs that list all of the SQL DataSource, SQL Statement, and SQL Transform builders present in the model. Choosing a builder name for one of these inputs causes the SQL Call builder to use the selected builder at generation and runtime rather than its "internal" builder. For example, if you needed the SQL DataSource to behave differently than the "internal" DataSource, then you would add an SQL DataSource builder call to your model, configure it appropriately, then select it as the override for the "SQL DataSource" in the SQL Call builder call. SQL Call will thereafter use the SQL DataSource builder call that you added to the model.

Parent topic: SQL Call builder

---

Library | Support |