HOW TO: Use a source field as a file name in FTP import
In this scenario, you're doing an FTP import and want to use the source field in the file name.
You would put this in the File name field of your import:
Not an array (classic UI):
{{data.fieldname}}
Array (classic UI):
{{data.0.fieldname}}
Not an array (beta UI):
{{record.fieldname}}
Array (beta UI):
{{rows.0.record.name}}
Our beta UI also supports: batch_of_records.rows... when the NetSuite export Batch size limit is greater than 1.
To include a timestamp, try using the Unix timestamp option {{timestamp(X)}}. You could also use {{uuid}} for a generic unique value.
You can also reference the import name via {{importName}}.
0
Comments
Hi Courtney.
I was really having issues getting this to work this morning. I used AFE 2.0 and this path finally worked. {{batch_of_records.0.record.eventObjectReference}} I had to use batch_of_records. The flow originates with a webhook listener.
Maybe {{rows}} is a NetSuite export thing?? It's all very confusing still. Is there a concise reference to the object model within IIO?
Hi, David. That new data structure nomenclature came online in June, and it should be apparent in the sample exported records:
https://docs.celigo.com/hc/en-us/articles/360045323471-integrator-io-release-notes-v6-6-1-0-June-2020#enhanced
We're trying to catch up with the existing code samples, but for the near term, you should be able to use "data" references, in AFE 1.0 at least.
Sorry for the trial and error, but I'm thrilled to read about your progress.
hi guys, for file name in ftp imports, is that using afe 1 or 2?
we can't seem to get the ff to work:
batch_of_records.0.record.fieldname
batch_of_records.0.record.0.fieldname
batch_of_records.0.data.fieldname
batch_of_records.0.data.0.fieldname
record.fieldname
data.fieldname
record.0.fieldname
data.0.fieldname
update on this, we were able to make it work by adding file encoding and using following syntax:
Please sign in to leave a comment.