Click here to speak live with a FuseBuilder Operator
Live chat by Boldchat

Single-User Licence: $95 

Multi-User License: $350 

Using FuseQueries

FuseQueries is an optional feature that can be used during the Architecting stage of FLiP. It allows you to use the database definitions in your project, along with the IO elements in the Fusedocs, to automatically create a working SQL query in the generated fuse.

There are four requirements to be able to use FuseQueries in a project:

  • You must have defined a database in the project.
    In Project View there is a sidebar link to "Define DB Tables". Clicking on this link will take you to the area where you can set up Tables and Columns for your project. You must have at least one Table with at least one Column to be able to use FuseQueries in the project.

  • You must have enabled FuseQueries in the project.
    In Project View or the "Current Projects" list there is a link to edit the project's properties. In this form you'll see a link to 'Use "FuseQueries"'. This box must be checked to use FuseQueries in this project.

  • The prefixes of the fuses with which you want to use FuseQueries must be found in your Config's "Model Fuse Prefix List".
    From any page click on the sidebar link "Config" and navigate down the page till you see the form inputs for "Model Fuse Prefix List". Separate multiple prefixes with a comma, and no space (for example "qry,act").

  • The fuses that will be using FuseQueries must have a recordset element in IO Outs.
    If the query type is going to be "delete", "insert" or "update", it's not necessary to have any child elements in this recordset.

Picture of the FuseQueries form, which allows you to build a query from Fusedocs
The FuseQueries form page allows you to map any incoming IO
Elements and any IO Elements in an outgoing recordset with
Tables and Columns from your project's database definitions.
  1. Select box to specify the type of query - "select", "insert", "update" or "delete".
  2. Incoming IO Elements can be mapped to a Column for use in a "where" clause, for use in a "insert" query to specify the inserted values and their columns, or in an "update" query to specify the columns being updated and their new values.
  3. The type of condition for a "where" clause, such as "like", "in", or "equals".
  4. IO Elements in an outgoing recordset can be mapped to a Column for use as the column being selected in a "select" query. In addition to regular table Columns, you can also specify "Calculated" (where the column in the recordset is a result of a calculation like "COUNT" etc, or a sub-query) or "@@identity" (for use in an "insert" query when you also want to return the newly inserted primary key).