FLAT
CouperSevenval TechnologiesDocker ImageGithub
develop
develop
  • Changelog
  • FLAT
  • Administration
    • Configuration
    • Docker
    • Logging
  • Cookbook
    • Using the Built-in Mocking
    • Performing Additional Checks on JWT Access Tokens
    • Logging Custom Fields
    • Using Environment Variables
    • Handling Errors with an Error Flow
    • File Serving
    • Forwarding a Request to an Upstream API
    • Extracting Common Initialization Flow Tasks
    • Encoding and Decoding JWT
    • Passing Header Fields to the Client
    • How can I pass an arbitrary header field to an upstream system?
    • Performing Additional Checks on JWT Access Tokens
    • Proxying requests to Upstream APIs
    • Increasing the Request Timeout
    • How can I see what the client requested?
    • Using Swagger UI for API Documentation
    • Testing API Requests
    • Testing with Backend Requests
    • Testing Templates
    • Sending POST Requests
    • Processing Upstream Responses
    • Protecting Access using JWT Tokens
  • Reference
    • Configuration
    • Debugging
    • flat CLI
    • Flow
    • Variables
    • OpenAPI / Swagger Integration
    • OpenAPI
      • CORS - Cross-Origin Resource Sharing
    • OpenAPI
      • Differences from Swagger
    • OpenAPI
      • Mocking
    • OpenAPI
      • Routing
    • OpenAPI
      • Security
    • OpenAPI
      • Upstream APIs
    • OpenAPI
      • Validation
    • Flow Actions
      • assert Action
      • auth Action
      • backend-flow Action
      • copy Action
      • debug Action
      • dump Action
      • echo Action
      • error Action
      • eval Action
      • log Action
      • nameshave Action
      • pass-body Action
      • proxy-request Action
      • regex Action
      • request Action
      • requests Action
      • serve Action
      • set-config Action
      • set-env Action
      • set-response-headers Action
      • set-status Action
      • sub-flow Action
      • template Action
      • test-request Action
      • xslt Action
    • Functions
      • apply-codecs()
      • array-reverse()
      • array()
      • base64-decode()
      • base64-encode()
      • body()
      • calc-signature()
      • capitalize-first()
      • content()
      • decrypt-xml()
      • decrypt()
      • encrypt()
      • ends-with()
      • file-exists()
      • fit-document()
      • fit-log()
      • fit-serialize()
      • get-log()
      • has-class()
      • html-parse()
      • join()
      • json-doc()
      • json-parse()
      • json-stringify()
      • json-to-csv()
      • json-to-xml()
      • jwt-decode()
      • jwt-encode()
      • ldap-lookup()
      • ldap-query()
      • lookup()
      • matches()
      • md5()
      • replace()
      • sort()
      • split()
      • tolower()
      • toupper()
      • trim()
      • unixtime()
      • urldecode(), url-decode()
      • urlencode(), url-encode()
      • uuid3() and uuid4()
      • verify-signature()
      • verify-xmldsig()
      • xml-parse()
      • xml-to-json()
    • Templating
      • {{,}}
      • Comment {{// …}}
      • Dot {{.}}
      • Conditional `{{if <condition>}} … {{elseif <condition> }} … {{else}} … {{end}}
      • loop
      • ?? Operator
      • Object XML Notation (OXN)
      • Pair Producer {{: …}}
      • Placeholder
      • Template Variables
      • with
    • Testing
  • Tutorial
Powered by GitBook
On this page
  • Using a JSON file
  • Debugging
  • Examples

Was this helpful?

  1. Reference
  2. Functions

lookup()

Previousldap-query()Nextmatches()

Last updated 5 years ago

Was this helpful?

string lookup(string fidj-file-uri, string key [, string default = ""])

The XPath function lookup returns the value associated with the key in a database file. The database file specified by the fidj-uri can be either in JSON or format. If the key is not found, the default string will be returned.

  • fidj-file-uri: FIDJ URI pointing to a local database file. The extension

    of the database file must be either lowercase .json for a JSON file or lowercase

    .shmt for an SHMT file.

  • key: database key to search for

  • default: optional value to return if the

    key is not found in the database (default is an empty string "")

Using a JSON file

The JSON DB file has to be implemented as a key-value object (SHMT does this automatically):

{
  "key1": "value1",
  "key2": [1, 2, 3],
  "key3": {"k":"v"}
  ...
}

If a value is either of type object or ordered list of values (array), the value is always converted to a JSON string. By using the function, the result string can be translated into a corresponding XML structure.

Example:

  <xsl:value-of select="lookup('fit://site/databases/db.json', 'key3')" />

would result in the string "{\"k\":\"v\"}".

Debugging

Examples

...
  <xsl:value-of select="lookup('fit://project/db/my.json', 'full_name', 'John Doe')" />
...
  <xsl:value-of select="lookup('fit://site/databases/db.shmt', 'key')" />
...

The lookup XPath function provides many information or error messages in the json .

SHMT
json-to-xml()
debug channel