1

I'm a System Admin in an org and today our Flow was throwing errors saying no such field RecordType.DeveloperName. I tried running a SOQL query using that field in Developer Console and I get same error if I run the query using Tooling API. If I uncheck Tooling API query runs fine. The error from the Flow is below.

ERROR at Row:1:Column:8 No such column 'Developername' on entity 'RecordType'. If you are attempting to use a custom field, be sure to append the '__c' after the custom field name. Please reference your WSDL or the describe call for the appropriate names.

I can use the Tooling API in the SOQL to include all RecordType fields except the DeveloperName.

I don't know how these two errors are related but need to access RecordType.Developername in any case. Any thoughts on problem here?

  • is this V34 (summer 15 pre-release) or V33 or earlier? – cropredy May 20 '15 at 1:08
  • Spring 15 release. V33. But also, Im not setting API version with any code. I'm just running a Flow and/or Dev Console – user2451 May 20 '15 at 1:27
  • 1
    Not sure about the Flow part of this issue, but in Tooling API (v33 current & v34 Summer 15) object RecordType does not have field "DeveloperName". Hence you can not query it using Tooling API. salesforce.com/us/developer/docs/api_toolingpre/Content/… – gaiser May 20 '15 at 9:10
  • So this looks like a very unfortunate bug I'm afraid. I confirmed that running this in the Developer Console works as DeveloperName is GONE in v34. The problem is that the below conflicts. Furthermore the org is not upgraded to Summer '15 anyway AND when you look at the list of fields presented for RecordType in Flow FullName is not there, DeveloperName is, but the error is saying DeveloperName does not exist when running. We will talk with support today and update here accordingly. salesforce.com/developer/docs/api/Content/… – user2451 May 20 '15 at 14:05
0

This was a bug that Salesforce has fixed with a patch release shortly after I posted it. While the Tooling API doesn't have DeveloperName field it should not have had anything to do with Flows and it did.

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.