SOQL Query Builder - Add Ability to Traverse Relationship Fields

[AndyHaas]

Would love the ability to traverse to the relationship field for the filter conditions section

Example Query

SELECT Id, NamespacePrefix
FROM FieldDefinition
WHERE DataType = 'Picklist'
	AND (NOT DeveloperName LIKE '%__%')
	AND EntityDefinition.DeveloperName = 'Contact'

[paustint]

@AndyHaas - The issue is that EntityDefinition is some special thing in Salesforce where it technically is a relationship field but the metadata definitions salesforce returns treat it as a text field.

I think I have mocked these types of relationships to fake it in some other places, I will see if I can do the same here.

[paustint]

There are two issues here:

1. Entity definition is listed as text (but does have reference info - so it is fairly easy to have code work around this)
2. Related fields only show up in filters if they are also selected in the query

After fixing #1, #2 still has an issue - temporary workaround is to include any relationship fields from WHERE clause in the query. (see below)

The reason why all relationship fields are not included in filters is performance related - a huge list is really slow to render, but could probably be solved with a virtual scrolling list.

SELECT Id, NamespacePrefix, EntityDefinition.DeveloperName
FROM FieldDefinition
WHERE DataType = 'Picklist'
	AND (NOT DeveloperName LIKE '%__%')
	AND EntityDefinition.DeveloperName = 'Contact'

[AndyHaas]

I didn't think I saw this on Standard Objects either. I just happened to be on the Entity object as I saw this.

[paustint]

This issue has been resolved.

1. All related fields one level deep will be automatically available in query filters and order by dropdown
2. If you visit an object more than 1 level deep (even if you do not select any fields) the object's fields are available for query filters and order by
3. Restoring a query should work properly for related fields included in query (AFAIK the level of traversal should not matter, tested up to 3 levels and it worked)
4. Field dropdown for filters and order by uses virtual scrolling since the list can be pretty huge and caused performance issues otherwise
5. EntityDefinition and other similar "text" fields that also have relationship information now show up in Jetstream is normal related objects that you can traverse