Append comments Field

[Jbid]

Please consider adding a feature to get to the appended comment history from a sharpoint list comment filed with append and versioning turned on to appear in a power app card?

https://powerusers.microsoft.com/t5/PowerApps-Forum/Append-comments-Field/m-p/34968#M14383

[jchivall]

This request has been open for two years with no ETA in sight. This is a major barrier for my organisation moving to Modern UI, PowerApps & Flow to replace InfoPath/legacy workflows. Very disappointing that this obvious functionality isn't available yet.

---

---

[NikitaKurguzov]

If anyone is looking for custom solutions in the meanwhile, check out Plumsail Forms - we did add an ability to see all the comments, and even have a discussion on SharePoint form

https://plumsail.com/docs/forms-sp/how-to/add-discussion.html

[AIUYM19]

I think the PowerApps team has either forgotten about this idea, or they are ignoring it. Two years with no movement—or even official comment—on an idea with over 200 votes is unacceptable.

This functionality is an absolute must in PowerApps, if you're going to connect it to a SharePoint data source. Without this functionality, attempting to set up a discussion field in a SharePoint list is futile.

[DawidWisniewski]

22 months "under review"... This is what I made using powerapps HTML field and send an HTTP request in FLOW, it looks almost the same way as modern view:

The biggest downfall of this solusion is that you have to wait for FLOW to trigger to see your newest comment.

Later I will maby make a topic with tutorial how i made this

[Jbid]

@DawidWisniewski Nice idea, looking forward to the write up! 

[danfoxley-tc]

https://www.c-sharpcorner.com/article/display-appended-comments-version-history-from-sharepoint-list...

[AIUYM19]

@DawidWisniewski I followed a very similar (probably almost identical) approach. I set up a Flow that is triggered by a change in an item in the SharePoint list. It gets the new data via an HTTP request, then appends it to a text field in a new SharePoint list. PowerApps then refers to the text field in this new list.

While it seems to work, there are several downsides to this approach.

• You need to maintain a separate list with a matching key field.
• You need to add an additional data source to your PowerApp.
• You need to ensure matching permissions on an additional SharePoint list.
• It can take up to 5 minutes for Flow to update the aggregated list item.
• You need to nest forms in PowerApps to use the second data source.

I'll be interested to read your write up to see your methodoloogy.

[CatWill]

PowerApps should add to the functionality of the existing product, not take away from it. 

[jchivall]

Another 7 months and still no movement on this. Looks like PowerApps still isn't worth using with SharePoint. With InfoPath deprecated, what are we supposed to do?

[AIUYM19]

@jchivall 

I don't think this is going to get traction with the PowerApps team anytime soon, unfortunately. My method above using a combination of PowerApps, multiple SharePoint lists, and PowerAutomate (formerly Flow) does work in the meantime. The downside is that it's a bear to set up, and you have to have a pretty solid understanding of both PowerAutomate and SharePoint in order to properly implement and maintain/troubleshoot it. It also requires a pretty beefy PowerAutomate license, if your PowerApp is used frequently.