cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Frequent Visitor

Patch function doesn't work

I have a problem and i was searching a lot but i cant find a solution.

I have an SQL Table called "Orden_trabajo" with this columns.

--Date.--User--Equipment--Model

 

I'm trying to use the "Patch" function to create a register in a SQL database. but when i write this:

Patch('[dbo].[Orden_trabajo]'; Defaults('[dbo].[Orden_trabajo]'); {Date: Today() } )

 

The DataSource is underline, like this:  Patch('[dbo].[Orden_trabajo]'; Defaults('[dbo].[Orden_trabajo]'); {Date: Today() } )

and it says:

The data source is read-only, so the patch function cannot write to the

I dont know what i'm doing wrong or what is the problem here, because i have other table in othr application that works correct with that function.

There is a way that i could change the data source to not be read-only?

help, please

 

1 ACCEPTED SOLUTION

Accepted Solutions
Super User III
Super User III

@Msaldivar 

Several threads indicate this error can occur when the SQL table does not have a primary key.  Do you have a primary key for the table Orden_trabajo?  I can't see any obivious primary key based on your columns --Date.--User--Equipment--Model.  Let me know

 

Related Threads:

View solution in original post

3 REPLIES 3
Super User III
Super User III

@Msaldivar 

Several threads indicate this error can occur when the SQL table does not have a primary key.  Do you have a primary key for the table Orden_trabajo?  I can't see any obivious primary key based on your columns --Date.--User--Equipment--Model.  Let me know

 

Related Threads:

View solution in original post

Dual Super User III
Dual Super User III

The error message you are getting would suggest that the user you used as a connection account to the database in the SQL connector does not have Write access to the database.  Check the permissions in SQL to make sure you have write access for the connection account user.  I don't think your syntax is necessarily wrong its the permissions on the backend database.



-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.

Thank you so much.

That was the problem, i just add a new column as a primary key and it worked

Helpful resources

Announcements
News & Announcements

Community Blog

Stay up tp date on the latest blogs and activities in the community News & Announcements.

Power Apps Community Call

Power Apps Community Call- January

Check out the Power Apps Community Call for January 2021

PP Bootcamp Carousel

Global Power Platform Bootcamp

Dive into the Power Platform stack with hands-on sessions and labs, virtually delivered to you by experts and community leaders.

secondImage

Power Platform Community Conference On Demand

Watch Nick Doelman's session from the 2020 Power Platform Community Conference on demand!

Top Solution Authors
Top Kudoed Authors
Users online (11,700)