Problem with moving files from one app to another

🙏 Ask the Community
1

Hi, maybe someone can help me :slightly_smiling_face:

From the Intake Form app, I am creating a Project item and want to move files.
However, the files are mixed up:

  • Site Survey Photos should be pushed to the Site Survey Photos field
  • Utility Bill Photos should be pushed to the Utility Bill field

But right now, it’s the other way around.

image
image1920×560 94.2 KB

2

Hi @Sandra

I think this is a bug (@Leo) that has come up before and i thought had been fixed (I can’t actually find the previous issue now).

I assume if you just try and move one file it moves across correctly?

1 Like
3

If I am moving files connected with only one field in this automation, it is working.
But for 2 fields it is mixed up.

4

Yea I have found my test workspace from when this came up in October and it is doing the same for me interestingly (at least for me) the third file(if you had one) works fine, if you create a record in the same app it works fine and very strangely if you do the whole action in a script it still goes wrong! (i was looking for a work round but haven’t found one yet)

1 Like
5

So far, it seems the best method is to fire separate workflows that only interact with one field at a time, but that’s definitely not a long term solution. Something definitely seems amiss here.

6

Yea looking at my tests I did that last year created the record and a relation then triggered a flow in that app that got the details of the original and then used three separate update blocks to pull the files across:
CleanShot 2025-07-03 at 14.32.07

View Screenshot
View Screenshot1200×952 106 KB

What I think is happening is that when you ‘move’ files between apps it effectively re-uploads the file and gets new file ID’s and in the process it is getting them muddled up and therefore putting the wrong files in the various fields.

1 Like
7

for what it is worth, this seems to work:

const app = 56051;

var_fileone = _2541017___alpha_field_files_one_id;
console.info(var_fileone);
var_filetwo = _2541017___alpha_field_files_two_id;
console.info(var_filetwo);
var_filethree = _2541017___alpha_field_files_three_slash_id;
console.info(var_filethree);

const {data: fileCreation } = await tape.Record.create(app, {
    fields: {
        name: `${_2541017___alpha_field_name_value} - script`,
        files_one: var_fileone
    }
})

await tape.Record.update(fileCreation.record_id, {
    fields: {
        files_two: var_filetwo
    }
})

await tape.Record.update(fileCreation.record_id, {
    fields: {
        files_three_slash: var_filethree
    }
})
8

Yeah I figured you could break it up into separate fields, either via the UI or via the API, and the explanation of why it’s happening makes sense. Still feels like a bug :stuck_out_tongue:

1 Like