Help: Get attachments not working any more

[yiz]

It is working before. I can get each attachment in the Apply to each control:

You can see it is 'Body', capitalized and it works, I can get each attachment content. But now there is no capitalized 'body' and I cannot get the attachment content any more. the error message is cannot find the file.

Please help.

Thanks

[yashkamdar]

Hello Team,

I can see that you can get the attachments just fine as per your second screenshot using the "body" from the dynamic content.

I just tried it out and it works just fine. Do not worry about the capitalization stuff Body and body are both the same things.

Here is how I tried this out and was able to fetch the attachments exactly as you did in your second screenshot.

This worked just fine for me.

If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!

[yiz]

Hi Yashkamdar,

Thank you for the quick reply. The thing is it looks like work. But when you really to run it, it gave file not found error:

I export package and look at code. They are different:

workable Body: "splitOn": "@triggerBody()?['value']"

not work body: "splitOn": "@triggerOutputs()?['body/value']"

Any ideas?

Thanks,

[CFernandes]

@yiz 

Hey Mate,

Can you please try using the "Get File Content" and pass the Id.

If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!

[yashkamdar]

Hello Team,

I think you have not configured your action properly, I had run the same flow a couple minutes ago and it ran just fine for me.

See below-

Can you confirm that your action was configured as below-

If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!

[yiz]

Hi Yashkamdar

There is my flow configure. I did it many times before and they are working. But now it does not. The thing is the old flows are still working. When create a new one, it is not work since there is no 'Body' anymore.

[yiz]

Thanks CFernandes, I will try.

[Anonymous]

Hi all. I'm having this exact same issue. In one flow, attachments sent via email open fine for users, but in a subsequent flow process which was created to be near identical, the attachments do not open. When looking at differences between the two flows I can see that - for some reason I do not understand yet - there is a difference in the phrasing of some terms, just like @yiz mentioned above:

In the functional flow, the default terminology is:

@triggerBody()?['value']

And the terminology for the one that does not is:

@triggerOutputs()?['body/value']

This can be seen when peeking the code of the trigger, as well as by hovering over any of the default data fields entered. EG:

In the functional flow, the default terminology when adding the trigger ID to the 'Get Attachments' function is:

@triggerBody()?['ID']

And the terminology for the trigger ID in the 'Get Attachments' function within the broken one is:

@triggerOutputs()?['body/ID']

Is anyone able to shed any light on this? Why the default terminology has changed / is different from one flow to the other when they were both created to match each other? It definitely seems to be causing issues with little explanation as to why it has happened.