Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Replies with Get-PnPTeamsChannelMessages #1101

Closed
Clifra-Jones opened this issue Sep 13, 2021 · 1 comment · Fixed by #1885
Closed

Replies with Get-PnPTeamsChannelMessages #1101

Clifra-Jones opened this issue Sep 13, 2021 · 1 comment · Fixed by #1885
Labels
enhancement New feature or request

Comments

@Clifra-Jones
Copy link

Is your feature request related to a problem? Please describe.
When using Get-PnPTeamsChannelMessages you only get the 1st message and no replies. This is useless in an auditing sense.

Describe the solution you'd like
Either a) return all messages, including replies or b) have another function that returns the replies based in the MessageId that is returned with the primary message.

Describe alternatives you've considered
I don't see another existing function to do this. We could use the Graph API but that seems overkill when we have this PnP.Powershell module to use,

Additional context*
None.

@Clifra-Jones Clifra-Jones added the enhancement New feature or request label Sep 13, 2021
@Clifra-Jones Clifra-Jones changed the title [FEATURE] Replies with Get-PnPTeamsChannelMessages Sep 13, 2021
@milanholemans
Copy link
Contributor

milanholemans commented May 20, 2022

Hi @Clifra-Jones

When I'm using Get-PnPTeamsChannelMessage I do get all messages in the channel.

image

Apart from this, seems like there is indeed no way to get the replies of a message. I'm creating an extra cmdlet for this called Get-PnPTeamsChannelMessageReply. This cmdlet will be ready by tomorrow. Hope this solves your issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants