Timeline for Determine `SObject type` from relationship name without an exhaustive search
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 19, 2021 at 16:53 | comment | added | ipavlic |
It's the inverse of reading fields. Given a relation and an SObject instance, we can read the fields through getSObject and get. To write a field, we can use put and putSObject. However, if intermediate objects do not exist, I'd like to create them. It's all related to apexfp.org for which I'm writing a mapping function factory.
|
|
| Oct 19, 2021 at 16:43 | comment | added | Derek F | @ipavlic I think this is where we come to identigral and sfdcfox's request for more information. Knowing the scenario you're trying to apply this situation to would be helpful. Probably the most helpful clarification would be "how are you getting the "Account.Id" string?" and "can you pass different/additional information?". If you could pass "AccountId" instead of "Account.Id", that'd make your life easier (or at least free you of the burden of that loop you want to avoid). | |
| Oct 19, 2021 at 16:28 | history | edited | Derek F | CC BY-SA 4.0 |
added 222 characters in body
|
| Oct 19, 2021 at 16:27 | vote | accept | ipavlic | ||
| Oct 19, 2021 at 16:27 | comment | added | ipavlic | Thank you for the confirmation! Unfortunately, general relations do not contain field names, but relationship names. | |
| Oct 19, 2021 at 16:24 | history | answered | Derek F | CC BY-SA 4.0 |