Hi @KoenJanssensPD
Understanding PostFollow and Follows:
The “postfollow” table (also known as the Follow entity) in Dynamics 365 allows users to follow records. It’s used for tracking user interests in specific records.
The “Follows” table is where the actual follow/unfollow data is stored.
Challenges with Patch on Follows Table:
You mentioned using Patch on the “Follows” table, but it resulted in an error. This is because the “Follows” table is not directly accessible as a data source in PowerApps.
The “Follows” table is part of the Dynamics 365 Web API, which isn’t natively supported in PowerApps.
Workaround Using Custom Connector and Flow:
While there’s no direct out-of-the-box (OOB) solution, you can create a workaround:
Custom Connector:
Build a custom connector in PowerApps that connects to the Dynamics 365 Web API.
Define actions for following and unfollowing records.
Power Automate (Flow):
Create a flow triggered by your custom connector.
In the flow, use the “Follow” and “Unfollow” actions from the Dynamics 365 connector to interact with the “postfollow” table.
Return the result to PowerApps via the custom connector.
Steps Summary:
User clicks a button in your PowerApp to follow/unfollow a record.
PowerApps calls the custom connector.
The custom connector triggers the Power Automate flow.
The flow interacts with the Dynamics 365 Web API to follow/unfollow the record.
The flow returns the result to PowerApps.
Remember, this approach involves creating a custom connector and setting up a flow, but it provides a way to achieve the desired functionality.
Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.
Sunil Pashikanti - Tech Blog: PowerApps
