Unanswered

Patching to SQL: data types wont match up

(0) Share

Report

Posted on by RhysD

Hi all,

Hope all's well. I'm working on a power app at the moment where I'm patching some data from and to a SQL table, the problem I'm having is that the patch throws back an error saying that the data type is wrong.

I've tried changing the data type directly within the patch by using Value() and DateValue(), but that didn't seem to work. I also tried changing the datatype and associating it with local local variables, which I then used in the patch, but that didn't seem to work either.

Ie. Patch(Source, {Date: DateValue(SourceDate), Number: Value(SourceValue)})

Any idea's as to what might be wrong?

All the best!

Rhys.

Categories:

Building Power Apps

All responses (4)

Answers (0)

Sort by

Pstork1 69,661 Most Valuable Professional on at

Like
a
(1)

Report
Copy link

Link copied!

SQL has a number of Date and Number data types. What specific data type is the field in SQL. Not all of them are compatible with Power Apps. Also, normally you need a second parameter on the Patch to specifically identify the SQL record you are updating.
RhysD 42 on at

Like
a
(0)

Report
Copy link

Link copied!

Thanks, that gave me a much better lead. I've managed to get past the original error now by double checking the record that was put in, however I now have another error.

The table it's going into requires a text field filled out that isn't within the form, it's effectively a default value that's needed for each entry, I've tried to supply the value directly but it's still saying that it requires data. Any ideas? It doesn't specify that the data type is wrong, just that it can't see it.
(formatting below).
mogulman 764 on at

Like
a
(0)

Report
Copy link

Link copied!

Is this Azure SQL? It is correctly formatted. I have a similar field.

ErrorMessage: "",

Defined by
[ErrorMessage] [varchar](256) DEFAULT('') NULL,

I would create an INSERT statement that duplicates the Patch and run it from SSMS. It is possible you are not fully defining the data required to insert data.

If this is on-premise SQL Server run SQL Profiler and see what is going on.
RhysD 42 on at

Like
a
(0)

Report
Copy link

Link copied!

weirdly enough, when I add in the AuditSource twice is throws back an error saying it's already been defined:
My colleague thinks it's a formatting error, but we're both a bit stumped with it.