[SalesForce] Cannot Access RecordType.DeveloperName Field as System Admin

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?

Best Answer

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.

Related Solutions

[SalesForce] API Access to Google Doc Attachments

Finally figured this out: you must contact Salesforce.com Support to have API Access to the GoogleDoc object enabled for a given org. Once this was done, everything worked as expected.

[SalesForce] Trying to create QuoteDocument via API failes

Interesting... I have some ideas, too much to put in a comment.

Add sforce.debug.trace=true; to the beginning of your method.

Regarding the API version don't be so sure you're using v. 26, check https://stackoverflow.com/q/23556030/313628.

Any special reason why it has to be done in javascript and not pure VF + apex?

insert new QuoteDocument(
    Document = Blob.toPDf('Test PDF content'),
    QuoteId = '0Q070000000OjV9'
);

Some <apex:input> field with should work too and be much cleaner... And if you don't want an inputField but JS way is giving you hard time you could still try with marking an apex method as webservice (oldschool way) or remoteaction. Server-side code should bypass any weird "no-Profiles-but-still" security settings in PE (I've recently had a security review and had to slap CRUD checks all over the place. Turns out managed code was bypassing the PE's "security by page layout" just fine like in orgs that really have Profiles).

Last but not least: what are you getting when you execute this (or matching describe operation in Ajax toolkit)?

Schema.DescribeSObjectResult dsr = Schema.SobjectType.QuoteDocument;
System.debug(dsr.isAccessible() + ', ' + dsr.isCreateable());

Best Answer

Related Solutions

[SalesForce] API Access to Google Doc Attachments

[SalesForce] Trying to create QuoteDocument via API failes

Related Topic