- Categories:
File functions (AI Functions)
TRY_ TO_ FILE¶
A version of TO_FILE that returns NULL instead of raising an error.
Syntax¶
Use one of the following:
TRY_TO_FILE( <stage_name>, <relative_path> )
TRY_TO_FILE( <file_url> )
TRY_TO_FILE( <metadata> )Arguments¶
Specify the file by providing:
- Both
stage_nameandrelative_path file_urlmetadata
Only one of these methods can be used at a time.
stage_nameThe name of the stage where the file is located, as a string, in the form
'@stage_name'.relative_pathThe path to the file on the stage specified by
stage_nameas a string.file_urlA valid stage or scoped file URL as a string.
metadataAn OBJECT containing the required FILE attributes. A FILE must have CONTENT_TYPE, SIZE, ETAG, and LAST_MODIFIED fields. It must also specify the file’s location in one of the following ways:
- Both STAGE and RELATIVE_PATH
- STAGE_FILE_URL
- SCOPED_FILE_URL
Returns¶
A FILE, or NULL.
Usage notes¶
Returns NULL when:
- The supplied URL is not validL.
- The file is on a stage that the user lacks privileges to access.
- The supplied metadata doesn’t contain the required FILE fields.
Examples¶
Unlike TO_FILE, which raises an error on invalid arguments, TRY_TO_FILE returns NULL in this situation. It otherwise works exactly like TO_FILE.
The example below illustrates the behavior of TRY_TO_FILE when given an invalid file path, assuming that
the file image.png exists on the stage but the other two files do not.
Result:
For more examples of creating FILE objects from valid inputs, see TO_FILE examples.