> For the complete documentation index, see [llms.txt](https://docs.fabricplan.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fabricplan.com/documentation/plan/planning-sheets/how-tos/persist-planning-data-using-writeback/faqs-on-writeback.md).
# FAQs on Writeback
**a. If a user updates a data input column in reading mode and closes the report, will the latest data be available when reopening?**
Yes. Plan captures changes made to data input columns and stores them in the backend database. This works in both reading and edit modes. When the report is reopened, Plan retrieves the latest values and loads the report with updated data.
**b. How does row-level security (RLS) work in Plan?**
Plan respects the RLS defined in the original Power BI dataset. The Planning sheet displays only the rows that the user is allowed to see. RLS in Power BI applies to users with Viewer access in the workspace.
**c. How does Writeback work with RLS?**
Plan writes back only the rows visible to the user. If a user can see a limited set of dimension categories based on RLS, only those rows are written back. You can write back only the data visible in the Planning sheet.
**d. How is data stored when multiple users perform Writeback? When are rows overwritten or appended?**
Plan processes writeback operations sequentially. During writeback, Plan compares incoming rows with existing rows in the destination. If all dimension columns and values match, Plan overwrites the existing row. However, if you would prefer Plan not to overwrite rows during writeback commits, select Writeback only changes/Delta writeback as the writeback type. Under this mode, Plan retains previous values.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.fabricplan.com/documentation/plan/planning-sheets/how-tos/persist-planning-data-using-writeback/faqs-on-writeback.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.