Download Attachments O365 saves same name for every attachment

When I use the download attachments activity for O365 I get a List of Objects, all having the same Name und Fullname Attribute despite having different file names in the mail (see objects below):O365AttachmentLocalItem[2]
{
O365AttachmentLocalItem
{
Context = null,
CreationDate = [09/03/2024 17:59:41],
Extension = “pdf”,
FullName = “P3_48DF373B3C881EEEB7A422AF58B60328.pdf”,
IconUri = null,
ID = “XXX”,
IsFolder = false,
IsResolved = true,
LastModifiedDate = [09/03/2024 15:54:19],
LocalPath = “C:\xxx\AppData\Local\Temp\2\31gg5zis.0sh.pdf”,
Metadata = Dictionary<string, string>(0) { },
MimeType = “application/pdf”,
Name = “P3_48DF373B3C881EEEB7A422AF58B60328”,
SizeInBytes = 59370
},
O365AttachmentLocalItem
{
Context = null,
CreationDate = null,
Extension = “pdf”,
FullName = “P3_48DF373B3C881EEEB7A422AF58B60328.pdf”,
IconUri = null,
ID = “YYY”,
IsFolder = false,
IsResolved = false,
LastModifiedDate = [09/03/2024 15:54:19],
LocalPath = “C:\xxx\AppData\Local\Temp\2\3gbwzqlv.rtf.pdf”,
Metadata = Dictionary<string, string>(0) { },
MimeType = “application/pdf”,
Name = “P3_48DF373B3C881EEEB7A422AF58B60328”,
SizeInBytes = 53204
}
}

They do have different IDs, different sizes and different LocalPaths. I need to get the original names to safe the attachments with their real name.

@nbuc

just to confirm can you try changing the o365 version and check if issue persists

cheers

@Anil_G I can confirm that this behaviou also appears in other versions (tried on different minor and one major release).

@nbuc

can ou try with version 2.0.1 …we have this in production and we dont see any issue as such

if it persists …please provide the studio version, activity versions you tried and if it is occurring for any specific mail box or all to dig further

cheers

Still the same behaviour, also in the AttachmentNamesList attribute I can only see the same file name twice…Version of Studio is 2024.10.1.

Edit: I could not test version 2.0.1, we use the integration service and i do not have access to Client ID and secret, therefore can not set the 365 Scope.

Found the error, problem was in front of the pc.

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.