Hmmm, so am I overreacting? I don't think so. I think there is an issue with "all releases are backwards compatible" and I'm seeing and experiencing a few examples of this with Summer '15.
We are an ISV partner with an OEM application. We suddenly started getting an error in a Flow that essentially said "Field DeveloperName not found in object RecordType". What? RecordType is standard and DeveloperName is the Name field. Ran a SOQL query on this in the org and when we checked "Use Tooling API" the query errors with same error. When unchecked it runs fine. Ok...maybe?
We are talking about Flows and native queries not code. Code identifies what API version, other stuff doesn't. So this should have no effect.
@Peter Bender posted a completely unrelated question in the @Salesforce Flow Automationgroup but his conclusion so far is that in his org there was an "issue" whereas in other orgs it was fine. This is same thing we are seeing.
A MAJOR issue is that this app is deployed in other orgs and we DO NOT get this error. Yes, yes same version of the app. That's not good.
After a call with Support for our issue he eventually deferred it to a Known Issue
https://success.salesforce.com/issues_view?id=a1p300000008Xo0AAE This may be related...but why? And why not in other orgs? Support needs to close cases so not as interested in discussing the whys but some of us might be worried about that part of it....@Bill Takacs We have one of our Technical Evangelist with our ISV partners reaching out to
@Darrell DeVeaux directly as the next step. I'll message you separately.
