temporary name appear

[darana]

Hi,

I have created a flow that start when a document is put into a specific folder.

Usually the flow work perfectly, however from time to time it failed as it seems that the file name is not the same.

ie. file name is : TEST.pdf

in the error message, the file name is TEST.pdf.zwmarkn.

Seems to be that the flow start with the temporary name before the real name.

I have try to put a delay after the first action but the use remain the same.

Do you have the same situation? How can this be fixed?

Thank you so much for your help.

[Pieter_Veenstra]

Can you give a bit more details on how you upload your files?

Drag 'n drop?

Upload?

Also what is the size of the PDFs? Do only the larger files fail?

[darana]

Thanks Pieter,

What we usually do is a save as in this specific folder directly.

Files are not bigIssues comes on all Files are not big, between 10kb and 100kb only.

[v-yuazh-msft]

Hi @ darana,

Could you please share a screenshot of your flow’s configuration?

Could you share more about the run details of your flow?

I have made a test on my side and don’t have the issue that you mentioned.

The screenshot of my flow as below:

The flow would run successfully as below:

Please share more details to me so I could try to help you.

Please share more details to me so I could try to help you.

Regards,
Alice Zhang

[darana]

Thanks for your help.

Here is the beginning of my flow :

The error message I am getting is the following one : 

And that's the breakfdown of my flow failure :

[darana]

Hi,

Do you have any suggestion? Is my flow incorrectly created?

Thank you in advance for your help.

Nicolas

[darana]

So my issue persist and I think I have founded where the problem is coming from but no idea on how I can solve this. If anyone have a suggestion (except changing the way to save the file) this will be highly appreciate.

What I have found is the following:

When we are saving the file, it is saving the file first as "Partial Download" before the final file. See print-screen below:

Any idea on how to start the flow only when the final document is created?

Thanks for your help.

Nicolas

[Pieter_Veenstra]

You could probably add a consdition in your Flow that checks the type of the file and if it is set to partial download then  exit out of your flow.

[darana]

But if I do this, do you think the flow will start again when the file as been renamed to the final name?

Any idea how to configure flow to check type of file?

[Pieter_Veenstra]

Hi @darana,

Within the trigger you should get Dynamics content returned that includs the file type. I would initially add a variable that is set to the trigger data. That way you can fairly quickly identify the data that you need within the Flow run history.

You could even try and read data for the file that you expect to exist if this errors then the file isn't complete yet.

I would expect the flow to retrigger on completion.

[darana]

Thank so much for all your help Pieter.

I am a bit novice to flow, do you mind sharing an exemple on how I can add the variable to trigger the data and identify the data I need?

I have founded a workaround for the time being as we are only using pdf file by adding a condition that if the file name with extenstion finish by pdf, it will do the necessary action and if no it will do nothing.

However we might use this tools for others format, like xls, pdf, xlsx, ... and if there is any other possibility than to create the same condition for all format time, this would be lovely.

[Pieter_Veenstra]

I thkn you could potentially do a check on the file name ending with .partial. If it is not .partial then the file is complete.

[darana]

Thank you so much. I have tested with a new flow and it seems to work, but only if the initial trigger is "When a file is created or modified (properties only) and not with my initial one.

I'll try to create my entire new flow using this initial trigger and will keep you posted.

Thanks again for your help.

[darana · Accepted solution]

So, I got it finally worked.

The work around I have founded is the following :

-Create 2 step of action that look at the initial file and if the file does not exist ( as content or as ID), those step it will therefore run as "Failed" and with the action "Terminate" set as if the previous step have failed, this will end the flow and indicate it as "Succeeded", which means that when I upload one document in the Sharepoint, the document can be created temporary as 3 document + 1 final document. All 3 temporary document are getting automaticaly "Terminated" and the correct one use the flow.

Thanks for your help on this.

Nicolas

[Pieter_Veenstra]

You can probably optimize this slightly by using this idea:

https://sergeluca.wordpress.com/2018/04/11/trigger-your-flow-only-when-a-document-is-created-from-a-...