Timeline for Get components of a compound field?
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 16, 2020 at 17:58 | vote | accept | Adrian Larson♦ | ||
| Oct 5, 2021 at 21:50 | |||||
| Dec 28, 2018 at 20:48 | comment | added | David Reed | Yeah, I guess another way to approach it would be mostly heuristic. We know the component name pattern for any field of type Address or custom Geolocation. What does that leave out besides compound Name fields? | |
| Dec 28, 2018 at 20:39 | comment | added | Adrian Larson♦ | One thing you could do is check if the first word of the field name matches before getting any describes. | |
| Dec 28, 2018 at 19:57 | comment | added | Adrian Larson♦ | Well Avrom said Winter 19 was the target for release, so maybe it will come out soon. | |
| Dec 28, 2018 at 19:51 | comment | added | David Reed | Yeah, it's not great. The JSON version eats about half a second, the non-JSON version about a tenth. I don't know of a way to do it without iteration but I'd love to be wrong (I need this for a project too). | |
| Dec 28, 2018 at 19:49 | comment | added | Adrian Larson♦ | Oh man that's slow. I was hoping it might be possible to figure out without iterating every single field on the object. | |
| Dec 28, 2018 at 19:32 | history | edited | David Reed | CC BY-SA 4.0 |
added 778 characters in body
|
| Dec 28, 2018 at 19:24 | history | edited | David Reed | CC BY-SA 4.0 |
added 209 characters in body
|
| Dec 28, 2018 at 19:16 | history | answered | David Reed | CC BY-SA 4.0 |