Tech Battle Field

While working with one of the screen Save button, i see error while patching the SharePoint list data. After investigating the issue, I found it is due to old data that is pulled to the screen. As per Mozilla Documentation in the link , ETag is http response header to a version of a resource. It will help to save the time to avoid unnecessary transactions. If there is no changes in the content, it will not send response to the web server. So as there is no change in the List,  Etag will not send response to the web server and it returns the error. So when we save the list it throws error. To avoid the issue, we need to refresh the Data Source in the after Patching the list. In my Case, i have updated the Refresh as below. Path(<< DataSource >>,<< Item to be Updated >>,{<< Column >>:"Yes"}); Refresh( << DataSource >> ); After adding Refresh() function it worked as expected. Hope this helps.

While working on SharePoint integration with PowerApps, I got this error message for one of the user. After investigating the error following are few reasons for the errors, User might not have the read access to the data (i.e when we try to load the collections from SharePoint List to a collection on App Load or Screen Visible function). User may lost access or user not having access to the site/list/item that they are trying to update. There might be document locked on other users (while updating the document properties.). There might be issues with the data connections. We need to make sure user have the access to all the connection specially Load data or patch data connection. I have added a custom message using Notify function. I have got the issue as user access got removed for the list. After updating user permission issue got resolved.

 While working with PowerApps SQL connector, i got the error as “An error occurred on the server. Server Response: Not a valid connector Error response” as below. I have removed and re-added the connection for SQL server and tried to remove and re-add the table in the SQL and re-added the SQL connection. Issue not fixed. After investigating the issue further, I found out there PowerApps not support following data types, binary()     varbinary() image cursor   rowversion, hierarchyid,   sql_variant xml   Spatial Geometry Types - Spatial Geography Types, and table. I have used binary() type in my table. That is the reason I am seeing the issue. After removing the binary() column I am able to fix the issue.