Creating a query using the Landmark Transaction Builder

Use the Landmark Transaction Builder to walk you through the process of setting up your query.
Note: All Landmark Transaction queries will run with dataview off mode by default.
  1. From the Activity information section, click Build.

    The Landmark Transaction Builder dialog box is displayed.

    Note: The Import button is for importing connection values that you have saved to a file.
  2. On the Fields tab, specify this information:
    Data Area

    From the list of available data areas, select the data area to be used by the node.

    Module

    Specify the Landmark module that will be used in your transaction, for example, ss for StrategicSourcing.

    Object Name

    Specify the object that will be used in your transaction, for example, SourcingCompany.

    Action

    Specify from the list of actions that are associated with the specific module you are using, for example, Find.

    Action Type

    Select from these options:

    • CreateUpdateDelete: Create, update, or delete a record.

    • Single Record Query: Retrieve one record. This option is typically used in processes that update data.

    • Multiple Record Query: Retrieve all records that meet the specified criteria.

    • Relation Query: Query on a relation to the specified business object. If the relation is one-to-many, multiple records will be returned.

    Relation

    If an Action Type is set to Relation Query, use this option to select the relation on the specified business object.

    Key Fields

    The key fields associated with the Object you have selected are displayed in this field.

    Click > or the right-pointing arrow to individually select key fields for the query. When multiple keys are available, click add all to include all key fields.

    Key fields that you have selected are displayed in the Selected Fields/Values pane.

    Key fields are listed in a required order. You cannot specify a value for a key field if there are any previous key fields without values. For example, if you specify the value for the second and third key fields, but not for the first, this message is displayed: "<FirstKeyName> cannot be null." You cannot test or save the query without fixing any key field issues.

    To specify a value for the field, double-click the field from the list, or select it and click the Set field value button.

    Specify a value for the field. For example, if the Action is Add, specify the value to be added. If the Action is Find, specify a condition.

    To remove a field from the list, select it and click the Remove fields button.

    Non-Key Fields

    All other fields associated with the Object you have selected is displayed in this field.

    Click > or the right-pointing arrow to individually select key fields for the query or click add all to include all key fields.

    Fields that you have selected is displayed in the Selected Fields/Values pane.

    To specify a value for the field, double-click the field from the list, or select it and click the Set field value button.

    If the field being updated is a binary object such as PDF or image files, then the file content can be updated by specifying the file path in the value field using the syntax file://<filepath>. This uploads the file into the database.

    To remove a field from the list, select it and click the Remove fields button.

    Note: Non-key fields cannot be used with conditions. You must use filters instead.
  3. Change configuration for "Stop on application error" and/or "Stop on connection error," if necessary.

    Enable these option to stop the process and write an error to a log file in the case of a Landmark application error or an error when attempting to connect to Landmark. These options are enabled by default. Typically, you would disable them only when you want error handling performed through the process. For example, you might configure a node to handle errors from the Landmark node.

  4. Configure general properties for the Landmark node as needed.
  5. On the Properties tab, configure options if necessary.
    Run as User

    Specify the user taking the action for tracking purposes. The permissions of the configured user are applied. This field may contain a variable reference.

    Original Authenticated User

    Use this option with Run as User in a proxy situation. Run as User is the user to which the transaction is proxied, meaning the query will be run by this user. The Original Authenticated User is the user for which the proxy is being used.

    Filter String

    Use the filter string to search for non-key fields.

    See Specifying filter queries.

    Page Size

    Maximum number of records to be retrieved in the query.

    See Page size parameter.

    As of Date/Effective Date

    See As Of and Effective Dates.

  6. On the Test tab, test the query.

    When you use the Landmark Transaction Builder to generate a query, the resulting string is stored on the Test tab.

    You can also specify the query directly into the Test tab query string box.

    When you are ready to test the query, click the Test button. Analyze the results. If you are satisfied, click OK.

    You will be on the Landmark Transaction Field Value Handling dialog box.

  7. Use the Landmark Transaction Field Value Handling dialog box to determine whether to use variable or use hardcoded value for Data Area, Module, Object Name, and Action.

    Typically, you will select Use variable for Data Area and select Use hardcoded value for the others.