Add row into a table action ignoring "dot" character

(1) Share

Report

Posted on by faschimi

I've built a flow that reads the properties of a Sharepoint document library and exports all the data to an excel file.

There is a title field in this library which may contain a dot (.) in the string in some records. The string is correctly read through the "Get files (properties only)" action, but when the row is created in the excel file, the field content is truncated at the position of the dot.

Example of records with a dot in the title in the document library:

How the information is being recorded in excel:

I'm using the raw data from the previous step (in this case, Get files (properties only) action), is it necessary to use some function to treat the data and prevent truncation at the dot position?

Thanks!

Categories:

Building flows

I have the same question (0)

All responses (3)

Answers (0)

Sort by

Suggested answer

Michael E. Gernaey 53,963 Moderator on at

Like (3)

Report
Copy link

Link copied!

Silly question,

If you click on the row in Excel, is that really all the data that is in it, or is there data below it (that you just can't see as if its carriage returned???)

No. I am not aware of a reason why it would remove the rest of the string.

If you (just for checking), did a replace on any . and make it an _ does it write it correctly now?

Was this reply helpful? Yes No
SheelanB on at

Like (2)

Report
Copy link

Link copied!

You could use the property {FilenameWithExtension} instead of {Name}, unless that was something you wanted to avoid. I am assuming it is being truncated beacuse it is assuming the rest of the File name is part of the extension. But this could be an alternative option

Was this reply helpful? Yes No
Suggested answer

faschimi 60 on at

Like (1)

Report
Copy link

Link copied!

I managed to solve this by changing to the {Title} property instead of {Name}. I don't remember exactly why I selected {Name} on the first try, but with {Title} the entire string is written correctly in Excel. Thanks @SheelanB and @FLMike for the insights.

Was this reply helpful? Yes No