To add this action to an existing procedure, right-click on the Procedure, select \u201cAdd Action\u201d, then select \u201cLoad Variable from Project Output\u2026\u201d<\/p>\n
1) From the Project field, select the project to call. On the other hand, if the sub-project will return plain text, set the Output format to Text and the Character set to an appropriate value for the data being returned, perhaps ISO-8859-1. Regardless of the type of data the sub-project returns, place the data into a variable to be able to use it later in the project, by placing a \u201cSet Variable<\/a>\u201d action immediately after the \u201cLoad from Project Output\u201d action:<\/p>\n In this example, the XML returned by the sub-project is now stored in the variable XMLPackslip. If the sub-project returns a single text value, you may need to do a Left Trim<\/a> and a Right Trim<\/a> to remove any leading and trailing carriage return and\/or new line characters. Here is an example:<\/p>\n After this call, we set the value into the variable FolderID:<\/p>\n But the FolderID variable starts and ends with a CR\/LF (carriage return\/line feed), represented by \\r\\n.<\/p>\n We can apply a Right Trim and a Left Trim function to the variable, either in the definition or in the procedure, before setting the value returned from the sub-project into the FolderID variable.<\/p>\n![\"\"](\"https:\/\/alt2.minisoft.com\/support\/wp-content\/uploads\/2018\/04\/VarFromProj1.png\")
<\/a><\/p>\n
\n2) Select the type of input, from a component or from the procedure variable.
\n3) Set the Input format appropriately for the input data. If it is XML, the Character set will typically be UTF-8.
\n4) Add any parameters to be passed to the project. See the Calling Sub-Projects<\/a> article for more information about passing parameters and accessing those parameters in the subproject. Set the Output format for the type of data the sub-project will return.<\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n