We have a customer that has several large (many fields) external objects in their internal production environment. We need to do some development that will be very dependent on those object definitions but in separate development orgs.

I see that there is a separation of the "External Data Source" definition from the "External Object" definition. One of the "External Data Source" type options is "Salesforce Connect: Cross-Org".

Has anyone successfully setup custom objects (__c) in one org and exposed them in another org as external objects (__x) so code can be developed that is tightly coupled to the external object names?

Or any other suggestions on how to go about this?

  • Does this github lib help? SObjectFabricator although I'm not sure I fully follow the question – cropredy Nov 10 '17 at 23:37
  • @cropredy Perhaps, but was thinking of a mechanism where queries can be run rather than the queries having to be replaced by mocked responses. – Keith C Nov 11 '17 at 0:06

Consider using Apex Connector. I would recommend because then you have the freedom to create mocked responses manipulating the behavior as you wish (with no DML though).

The other option would be using https://www.mocky.io/ (or similar) or creating your own service on Heroku, for instance.

| improve this answer | |
  • Keith specifically states that he doesn't want to mock responses! – Matt Lacey Jan 9 '18 at 3:20
  • 1
    Ok, I was under the impression he wanted due to the title. – Jeferson Chaves Jan 9 '18 at 9:57
  • 1
    Thanks Jeferson. I wasn't aware of the option of keeping it all in the org via the Apex Connector so that has some appeal... – Keith C Jan 9 '18 at 10:32
  • @JefersonChaves Fair point :) – Matt Lacey Jan 10 '18 at 4:10

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.