transformations:input
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
transformations:input [2021/03/19 17:44] – craigt | transformations:input [2021/03/28 15:15] – craigt | ||
---|---|---|---|
Line 1: | Line 1: | ||
{{ transformations: | {{ transformations: | ||
====== INPUT ====== | ====== INPUT ====== | ||
- | Category: Create / Input | + | Category: Create / Input\\ |
+ | |||
+ | \\ | ||
=====Description===== | =====Description===== | ||
- | This transformation | + | This action |
To simplify development, | To simplify development, | ||
+ | |||
+ | \\ | ||
+ | =====Use cases===== | ||
+ | The Input action passes data between modules in memory which helps avoid potentially slow reading datasets from disk or writing to disk in every iteration or call. By removing the need to read/write datasets to disk, the action simplified workflows.\\ | ||
\\ | \\ | ||
Line 22: | Line 28: | ||
\\ | \\ | ||
=====Populating the Input dataset from another project===== | =====Populating the Input dataset from another project===== | ||
- | An Input action called from another project cannot be // | + | An Input action called from another project cannot be // |
- | a .dset file export must be made from the calling dataset and imported into the Input action, or, the calling dataset must be copied to the clipboard and pasted into the receiving Input action. | + | |
- | + | ||
- | \\ | + | |
- | =====Use cases===== | + | |
- | Such a table can be used later for iterations, folder commands, or file commands.\\ | + | |
\\ | \\ |
transformations/input.txt · Last modified: 2021/07/18 02:03 by craigt