Patching null to SQL

[AParker]

I'm aware that turning on the experimental setting "formula-level error management" allows you to write nulls to SQL, but it breaks my entire app - the app quits working altogether with the setting turned on. Are there any workarounds?

-editing - on further testing, this isn't actually my issue at all. Can't figure out how to delete so please disregard, thanks

[Anonymous]

What are you trying to achieve? because if you just want a empty field in your sql database you dont have to put anything in there. for instance. I have a database with 2 columns. name and age. i use a patch like this

Patch('[dbo].[Person]'; Defaults('[dbo].[Person]'); {name: "Danny"})
In this case the column name would have Danny and the age column would say "Null". Plus i dont have any setting turned on that allows me to do this

[HarjitSamra]

I think he's referring to updating a field to NULL where it already has a value.

I've come across the same issue with SharePoint and date fields.

[Anonymous]

@AParker 
I just tested something. i have 2 text input called "txtName" and "txtAge".

and a button with a patch function in it

Patch(table1; Defaults(table1); {name: txtName.Text; age: txtAge.Text});;

And then i have another text input called "txtName2" and a button with a patch function 

Patch(table1; Last(table1); {name: txtName2.Text; age: Blank()});;

What this does is update the name in the last row you added and update the age to a blank field. Hope this helps

[Anonymous]

LOL, i accidently skipped over the -editing- part

[HarjitSamra]

Haha - yeh, me toooooo!