Timeline for Format for including @api recordId in JSON.parse
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 15, 2023 at 16:52 | comment | added | ddeve |
Missed that piece thought just ellipses. Still not working but now wondering if because I'm trying to pass the recordId to an autolaunched Flow? Doesn't seem like I should be having so much trouble with this part. When I include recordId as another property I'm either not using correct syntax to pass {!recordId}, which is not accepted in LEX page, or I don't see it if leaving assignment out as docs suggest its passed automatically if on LEX Record page which it is.
|
|
| Apr 15, 2023 at 3:02 | comment | added | Adrian Larson♦ |
That's not what I have in my post though. The ... is a very important piece of the syntax. See spread syntax.
|
|
| Apr 15, 2023 at 2:18 | comment | added | ddeve |
Somethings not quite right with the syntax at least because return {JSON.parse(this.flowParams), recordId}; is giving me compiler errors. Parsing error: Unexpected token, expected ","
|
|
| Apr 15, 2023 at 1:00 | history | answered | Adrian Larson♦ | CC BY-SA 4.0 |