3
Personally, I would suggest that the solution is to be aware of the pitfalls of changing the Developer/API name of anything on the platform, and then not to do it.
Change the label by all means, but not the API name, as only problems will ensue. There are plenty of examples where Salesforce themselves have changes the name of something (Wave -> Einstein ...
3
You need at least one indexed field in order to avoid expensive table scans, and potentially query timeout problems or non-selective query errors.
You have two real options. First, use your first option. The OR operator will be just fine, as long as you're not filtering for null. The second option is to use the formula field, but request a custom index.
...
2
Parent references are not an Array, but a simple Object. No need to use [0].
row.Tasks[0].Owner.Name
2
You are going to have to post process the result - the owner name is there, but you will need to iterate through the array to extract it.
The reason you can't see it is because the query viewer is not capable of showing deeply nested objects - you need to serialize it to JSON and then examine that.
I wrote this little query to get the output below:
Contact[] ...
Only top voted, non community-wiki answers of a minimum length are eligible
