Salesforce

Magic xpa SQL Where and DB SQL Where Usage Considerations (Magic xpa 3.x)

« Go Back

Information

 
Created ByKnowledge Migration User
Approval Process StatusPublished
Objective
Description

Magic xpa SQL Where and DB SQL Where Usage Considerations (Magic xpa 3.x)

When using virtual columns from the current task in the SQL range, the virtual columns must receive their values from the calling task’s properties, otherwise their default values will be used.

Note:

The init expression is calculated afterwards; therefore it cannot be used.


BLOBs cannot be used in the SQL range.

Magic xpa does not check the syntax of the SQL range. Therefore, if an invalid SQL syntax is used, a message from the RDBMS will occur in Runtime.

Magic xpa does not check the attribute of each column used in the SQL Where string. It tries to convert each attribute to a string which is concatenated in the corresponding location in the SQL Where string. Therefore, it is important to use the attributes properly.

When the Link Join operation is used, Magic xpa uses an alias for the Table names. Therefore, instead of Table1.Column1, it uses A.Column1. If a string is written in the DB SQL which contains a column name, the alias letter corresponding to the Table should prefix the column name.

Magic xpa suppresses any trailing blanks.

The DB SQL Where range and the Magic xpa SQL Where range are computed once, before the Task Prefix.

Related Topics

Reference
Attachment 
Attachment