Collaborating in Power Apps: Mastering the Comments Feature
Enhance team communication and streamline code reviews with Power Apps comments—learn how to use threads, mentions, and track changes effectively.
Comments in Power Apps Studio are a lightweight collaboration tool designed for team development. Unlike traditional code comments that explain logic inline, these comments are stored in Microsoft Dataverse and follow the app wherever it’s shared—but not when exported to another environment. Their primary purpose is to facilitate code reviews, hand off tasks, and keep a clean audit trail of feedback.
In this guide you’ll learn how to use comments effectively by walking through a realistic scenario, understanding the underlying data structure, and avoiding common pitfalls.
Understanding the Comments Feature
Comments live at the screen or control level. Each comment can start a threaded conversation, and you can tag colleagues using the @ symbol. When you mention someone who hasn’t been granted access to the app, Power Apps will prompt you to share it with them and send a notification.
Key characteristics:
- Comments are not a substitute for inline documentation. They are stored in Dataverse and do not travel with the app when using solutions or exporting.
- Each thread has a state: Open (active discussion) or Resolved (closed).
- The comment UI is located in the right‑side panel of Power Apps Studio, accessible via the speech‑bubble icon.
- You can delete comments, edit them, or resolve threads from the same panel.
A Real‑World Scenario: Travel Request App
Let’s imagine you’re building a “Contoso Travel Request” app. On the RequestScreen there is a SubmitRequest button that is currently disabled (DisplayMode = Disabled) until every required field is filled. A teammate suggests that the button should always be enabled so users can see validation error messages. You want to discuss this change without creating a formal ticket.
We’ll simulate the conversation using comments.
Step 1: Create a Comment
- Open the app in Power Apps Studio and navigate to RequestScreen.
- Select the SubmitRequest button.
- Click the Comments icon (speech bubble) in the top‑right corner.
- In the panel, click New comment.
- Write a message explaining the suggested change. Use
@to mention the developer responsible for the button logic. - Click Add comment.
Step 2: Reply & Resolve
The mentioned developer picks up the task, changes the button’s DisplayMode to DisplayMode.Edit, and adjusts the validation text. They then reply to the thread:
To keep discussions tidy, keep each reply focused on a single point. Avoid mixing multiple issues in one thread.
After the change is verified, the original author (or any participant) can resolve the thread:
- Open the comment panel.
- Click the three dots next to the thread.
- Select Resolve thread.
The thread will turn grey and a checkmark will appear, indicating it’s closed.
Where Comments Are Stored: The Dataverse Comment Table
All comments live in a system table called Comment within your Power Platform environment’s Dataverse. This table is automatically created when you first use the feature. You can view it by going to make.powerapps.com → Data → Tables → Comment.
Below is a breakdown of the key columns. The actual schema may evolve, but these fields are the most relevant for everyday use.
| Field Name | Data Type | Description |
|---|---|---|
CommentId | GUID | Primary key, auto‑generated. |
AnchorId | GUID | The ID of the object the comment is “attached” to (screen or control). Used to group comments under the same parent. |
ArtifactId | GUID | The unique identifier of the Power Apps app (the canvas app). |
Body | JSON | Stores the entire thread content (messages, mentions, timestamps) as a JSON string. |
Kind | Choice | Identifies whether the record is a Container (holds the thread) or a Thread (individual message). |
State | Choice | Either Open or Resolved. |
Because comments are stored in Dataverse and not inside the app’s .msapp file, they will not be exported when you package your app into a solution. Never rely on comments to explain complex formulas—instead, use clear naming conventions and the Description property on controls.
Security & Performance Considerations
- Mentions & sharing: When you
@mention someone who doesn’t have access, Power Apps will offer to share the app with them. This is convenient but can accidentally grant broad access if not carefully reviewed. - Environment isolation: Comments are scoped to the environment. If you copy an app to a different environment (via managed solution or manual import), all comments are lost.
- Performance: The comment panel loads asynchronously. For apps with hundreds of threads, you may experience a slight delay when opening the panel. Resolve or delete obsolete threads to keep the panel lean.
Common Pitfalls to Avoid
-
Using comments as inline documentation As noted, comments do not travel with the app. If a developer moves the app to a new environment, all context is gone.
-
Forgetting to resolve threads Stale, unresolved threads create clutter. Make it a habit to resolve a thread once the action is completed.
-
Mixing multiple issues in one thread When you need to discuss two separate changes, create two threads. This makes it easier to track progress.
Best Practices for Team Collaboration
- Use comments for code reviews: Point out specific controls, mention the developer, and describe the expected fix.
- Keep threads short: Limit each thread to one topic. Use replies to narrow down the solution.
- Resolve promptly: Once a change is verified, resolve the thread. You can always reopen it if needed.
- Audit regularly: Periodically review open threads to ensure nothing is forgotten.
Final Recommendation
Power Apps comments are a powerful tool for real‑time collaboration during app development. When used deliberately—for feedback, task assignments, and code review—they improve team velocity without adding overhead. Reserved for action‑oriented discussions, they complement (not replace) a proper version control and deployment strategy.
References
- Original source article: Power Apps Comments: Collaborate & Give Feedback by Matthew Devaney
- Microsoft Learn: Comments in Power Apps (official documentation) (verify URL)
- Dataverse overview: What is Microsoft Dataverse?
Learn how small coding practices—like using descriptive names, flattening conditions, and simplifying logic—can make your apps easier to update and less error-prone.
Move past the gallery and discover the hidden patterns for validation, navigation, and smart submission handling in your data entry forms.
PowerShell unlocks admin capabilities that the Power Platform admin center simply doesn’t offer—from recovering deleted apps to blocking trial licenses. Here’s how to wield them safely.