Export into Excel File - file path too long

Hello guys! how are you all doing?

I’m getting an error when trying to export into an Excel file [see attached]

I’m unsure how the EasyMorph “export into [files]” happens, but it seems that it tries to create a temp file in the destination folder and with a filename as [UUID & “.em.temp.xlsx”].

This temporary name alone gets to be 50 chars long;
adding it to the original [file_path] used, it can make the [full_file_path] too long and, as a result, impossible for the temporary file to be created, which in its turn throws a missing part of path error.

// +++
Suggestion: Can’t EasyMoprh uses a local folder (like the one available as the Environment Variables “TEMP”) to create these temporary files and, then, move the final/treated file to the original destination folder?

Just because the file does exists in that dedicated shared directory, within the file_path length limitation and it is just when EasyMoprh tries to create the temporary file that the issue arises.
+++ //

Bear in mind that I do know that file paths shouldn’t be this long.
It is just that I, an end-user, am unable to amend these issues without the propre access-rights (I.T./admin):

(1) the redacted part is a mapped drive that, sadly, is not mapped equally between all employees - for some reason, people from other countries have a mapping of their own; and
(2) the rest of it is a shared folder that will change in accordance to the YEAR and MONTH we’re currently in and is generated automatically by certain I.T. jobs each EoM.

This is just a suggestion. I’m sorry if not a good one and if I made you lose time on reading it :laughing:

Hello @Felippe.Costa,

We have discussed this issue internally and decided that it's not feasible to change this behaviour. We have chosen to write the temp file to the same folder as the target file because this narrows a number of edge cases when the export will fail (if the folder is absent or not writable, the export will fail in any case).

As a workaround, you could try to export the data to one of the parent folders, or to a different folder, and then move the file to the target folder using the "File command" action. Please make sure to use a folder on the same drive as the target folder to improve the reliability of the workaround.

Hello, @andrew.rybka
Thanks for taking the time to answer :slight_smile:

That’s seems a good idea indeed.
I can get the current user temporary folder path from System Information action;
Use it to save the export;
And then move it from the Temp Folder to the Intended Folder by using the File Command action.

Seems about right.
Great. Thanks again for the answer (and suggestion)

Have a good day sir!

Hello @Felippe.Costa,

You're very welcome! Have a great day as well!