We have a component we developed some time ago, and needed to make some changes to it. In the sandbox we are using to develop the changes in, we are now getting an error when we try to save the component:

Failed to save MyComponent.cmp: Invalid definition for null:MyComponent: SELECT Id, IsActive FROM User ^ ERROR at Row:X:Column:Y No such column 'IsActive' on entity 'User'. 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.: Source

(Names and locations redacted to protect the innocent.)

Here is an absolutely bare-bones implementation that is failing in a separate, Summer '19 sandbox org:


public class failQueryController {
    @AuraEnabled public static User[] getUserList() {
        return [SELECT Id, IsActive FROM User];

Lightning Component

<aura:component controller="failQueryController">

The component fails to save with the same error message. Other fields, such as ProfileId, or Profile.Name, also generate this error.

Is there anything in the release notes about this behavior? Can it somehow be fixed? Should we report this to salesforce.com?

  • 1
    Could be this known issue that you are encountering.
    – Jayant Das
    May 14, 2019 at 19:10
  • 1
    @JayantDas That looks like it. If you add an answer, I'll gladly accept. Not sure why I didn't find this when I went looking for it.
    – sfdcfox
    May 14, 2019 at 19:11
  • 3
    It isn't every day somebody gets to answer a question from sfdcfox, @JayantDas. Well done. May 14, 2019 at 19:13
  • @SebastianKessel True that :)
    – Jayant Das
    May 14, 2019 at 19:14
  • i got resolved same issue with "recompile all apex classes"
    – sdandamud1
    May 14, 2019 at 19:36

1 Answer 1


You seem to have been impacted with this known issue: Field Integrity Exception when saving a Lightning Component in Developer Console which references User Fields. This is scheduled for a patch release per the issue details.

The workaround until patched as mentioned in the issue, is using Metadata API or SFDX/VS Code to deploy the changes.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .