We’re rewarding the question askers & reputations are being recalculated! Read more.
7

Assuming all the objects are already created, you could create a file that simply contains the one field definition you need, copy it, and deploy it. I'd say this task is probably easiest with Ant, but you could conceivably do it in an IDE as well. First, set up your package.xml: <?xml version="1.0" encoding="UTF-8"?> <Package xmlns="http://soap....


2

This was caused by our OData connector; it had a bug in handling ORs in its query.


2

You can change the field type for a custom field on an external object to a Lookup or Indirect Lookup to associate its values with a Standard object. Use a Lookup if the column in the external data holds Salesforce record ids, and an Indirect Lookup if it is a business key. Indirect lookups can only point to unique custom fields that are flagged as ...


1

Holy moly. I figured it out. It turns out that the solution was quite simple. Even though our custom fields that reference Account and Event have API names Account__c and Event__c they have to be referenced as Account__r and Event__r for salesforce to understand that you want to create that relationship. Makes sense, but should be documented better!!! The ...


1

External objects are really quite limited. It may be worth checking that link which is to official documents but it states that: Formulas and roll-up summary fields can’t reference fields on external objects. The only type of relationship you can have on there are lookup and external lookup, and indirect lookup relationships. But as far as mapping is ...


Only top voted, non community-wiki answers of a minimum length are eligible