Possible causes you should investigate
1)Excel table / data source permission boundaries
Even if the file is accessible, check if the table inside the Excel file is properly formatted as a table (required for Power Apps access).
Confirm that the connection used by the app has the right credentials and that the sharing/permissions of the file/table haven’t changed (owner, link, etc).
Because you as dev can access it, but others get “permission to access the row” — might be that the connection is using your credentials implicitly or that others lack “write” rights.
2) App’s connection/connector context
Check whether the app was built using your (owner) connection to OneDrive/Excel, and whether the end-users’ context is being used or overridden.
Sometimes apps using personal connectors work for the creator but fail for others. Consider using a service account or “shared connection” pattern.
Also ensure that the OneDrive file location and path haven’t changed (folder rename/move) which might break saved credentials.
3)Regional or data-source quirks
Because the backend is Excel in OneDrive, there may be limitations or changes affecting that pattern (e.g., concurrency, locked file, or recently Microsoft changed something in policy).
If the issue started at a specific time (Monday morning), check if any change occurred then: file moved, permissions changed, folder moved, tenant update, etc.
recommendation next steps for your case
1)Open the connection details in your Power Apps designer: see which connection (OneDrive, Excel) is used, and check if it’s using the correct credentials.
2)Review the sharing permissions of the Excel file: for each impacted user ensure “Edit” rights, and check if the file is shared via link versus direct sharing — sometimes link-sharing can have limitations.
3)In the OneDrive file, check the Excel workbook: is the table set up correctly, are there any row-level permissions, or is the workbook currently locked/open by someone (causing save to fail).
4)If you suspect the Excel/OneDrive pattern is brittle, consider moving data to a more reliable backend (e.g., a SharePoint list or Dataverse) for future stability.
Thank you!
Did I answer your question? Mark my post as a solution!
