Skip to Content

SADL = Service Adaption Definition Language.

A SADL query is a type of query that targets the database directly, and exposes all the required information to the UI.


Have you ever wonder why some OWL UIs have the “S” prefix, like COD_Account_SOWL? Yes… because they are SADL-based.

sadl_account.JPG

SADL queries are very useful, because they’re very easy to configure and very powerful at the same time. You can e.g. access your extension fields if your SADL query is based on a standard BO. You just need to create it via UI designer.

How to use a SADL query?

Once created, you just have to define the selection, basic find, and result fields.

sadl_query.JPG

Selection: fields to be available on the Find Forms, i.e. you can use to filter the result set.

Basic Find: the SearchText DataField will work for all the fields you check this column. For instance, if you check “Name” and “ID”, you’ll be able to search for both values via basic find.

Result: every field checked will go to the target DataList (your actual list exposed to the UI).

sadl_query_datamodel2.JPG

Some limitations:

  • You cannot use SADL queries in ECs.
  • You cannot re-use the query somewhere else.
  • You cannot execute the query via ABSL.
To report this post you need to login first.

1 Comment

You must be Logged on to comment or reply to a post.

  1. Nabarun Barua

    Hi Fernando Giroleti,

     

    Can you please explain Limitation little in details. Second and third is little confusing.

     

    Example:

    • You cannot re-use the query somewhere else.:¬†Does this mean, I can not use default Query of Business Object in ABSL code some where else. or if I create an Embedded Component for same Business Object. Does that means I can not use the Default Query of the Business Object.
    • You cannot execute the query via ABSL.: Is that means I can use Default Query of Business Object in ABSL code.
    (0) 

Leave a Reply