Timeline for Data Extension Data to JSON with SQL
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 28, 2020 at 6:16 | comment | added | Macca | I'm a bit confused. FOR JSON PATH will create a single JSON document that you'd not be using to update every record. What are you wanting to "push to another part of the business later on"? How is the data going to be pushed? If you just want those field placed into JSON, you could just use string manipulation. | |
| Jul 28, 2020 at 4:46 | comment | added | Trevor Van As | I tried to change it to Overwrite but I got the following error "Update Type must be 'Update' or the target data extension 'Health_Affiliate_Email_Capture' cannot appear in the query." | |
| Jul 28, 2020 at 4:36 | comment | added | Macca | FOR JSON PATH would create a JSON document containing an array of all the records in your Health_Affiliate_Email_Capture Data Extension. So the output contains one row, not a row for each id. If you're needing to output a JSON document, don't use a PK and just overwrite your results data extension and do a Data Extension Extract with no column header etc. There'd be only one column, "Data" in your results data extension and one row. | |
| Jul 28, 2020 at 4:17 | comment | added | Trevor Van As | Thanks! Just a quick follow-up to this. It won't let me save the query unless I reference the primary key field (id in this case), what's the best way to reference this? | |
| Jul 28, 2020 at 3:26 | history | edited | Macca | CC BY-SA 4.0 |
deleted 2 characters in body
|
| Jul 28, 2020 at 3:20 | history | answered | Macca | CC BY-SA 4.0 |