The Invalid SQL error is issued in the following situations:
<entity> is an unknown entity in <SQL>: you have a SQL query that is using an entity that no longer exists.
You have to fix the SQL associated with this query, in order to use an entity available in your application.
<attribute> is an unknown attribute of <entity> at <query>: you have a SQL query in your application that is using an attribute that no longer exists.
You have to fix the SQL associated with this query, in order to use an attribute available in your application.
Unknown <parameter> parameter in <query>: you have an SQL query in our application that is using a parameter that no longer exists.
Depending on your requirements, do one of the following: fix the SQL associated with this query, in order to use an available parameter; or change the input parameters of this query.
Parameters with no separating spaces found in <query>: your SQL query is using some parameters with no spaces in between. For example, SELECT @Parameter1@Parameter2.
You have to fix the SQL associated with this query, in order to have spaces separating your input parameters.
<text> is a reserved prefix in <query>: your are using system tables in your SQL query and this is not allowed for security reasons. The system tables are the ones that start with the following prefixes: osusr_, ossys_, and oslog_. If your query uses any of these prefixes in a condition, for example, this error is displayed.
You have to fix the SQL associated with this query, in order to remove the references to any of the above system tables.
Output structure must be set in <SQL>: you haven't defined the structure to store the result of the SQL query.
Edit this query and set its output structure. How?
Output structure cannot contain structures with nested Records / List: you have a SQL query whose output definition has nested records or lists.
You have to fix the Output Structure of this query by doing one of the following: use a different structure with no nested elements; or redefine this structure in order to avoid nested Records or Lists.
Parameters with 'Expand Inline' set to 'Yes' must be of 'Text' data type: you have a SQL query that is using inline parameters whose data type is not Text.
Edit the input parameters of this query and do one of the following: set the Expand Inline property of the input parameter; or change the data type of this input parameter to Text.
In the query ‘<SQL>’ the Foreign Entities are located in different databases: ‘<Foreign Entity 1>’, ‘<Foreign Entity 2>’,… in ‘<Database Connection A>’; ‘<Foreign Entity 3>’, ‘<Foreign Entity 4>’,… in ‘<Database Connection B>’; …: you are using Foreign Entities in the query that are located in different databases. Each SQL query can only use Foreign Entities located in the same database.
Edit the query and put each group of Foreign Entities in its separate query - the groups are detailed in the error message to help you. If you have joins between Foreign Entities that have to be separated, join manually the result sets.
Cannot use the query count output parameter. The SQL query '<SQL query>' must be a SELECT statement: you are using the Count output parameter of an SQL query that cannot return a query count result because the query is not a SELECT statement.
Review the logic of your application so that the query you are using is a SELECT statement and thus, have the query count filled with the number of records.
Clicking the symbol will take you directly to the parent action flow and highlights the SQL query that has the error.
About Error Messages