Odd issue with Set File Field - works fine - shows undefined in editor

Questions
1

I’ve got a workflow that triggers on a new file uploaded to a OneDrive folder. As part of the workflow, I need to get the file and upload it to an API. To do this I use:

  • A OneDrive file node that gets the value based on the file id from the trigger.
  • A Set File Field that - from what I saw in my research working on the workflow, is required if you want to upload those bits an API

My workflow works - yet when I’m looking at the Set File Field node, it always reports {{ data }} as undefined.

image
image570×397 16.4 KB

As I said, this works just fine, but I’m concerned that the editor seems to think it won’t. Anything I should know here?

2

It may show as undefined while setting up the workflow because no real data is available in workflow.
as you already mentioned:

3

Right, but I can run it, see it work successfully, open the node, and it still says that.

4

Could you share the workflow itself? This is how.

5

please share workflow so we can guide you better.

6

Sure - here ya go:

7

Shoot, you know, I had this system (Download file, set file field), based on a search result I found while building the workflow and I thought it was necessary. I duplicated my workflow, nuked that node, which honestly felt weird and unnecessary, and my flow works just fine. I apologize for the noise, but I’m happier my workflow is simpler. :slight_smile:

8

With what I found, it still works and is not green because it is not explicit reference like:{{ $('Download file').item.binary.data }} but direct reference making ui validator to fail but n8n engine recognizes it.
using direct references like (data), data, {data}, {{data}}, ((data)) all works which shows how powerful n8n engine is.

9

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.