I am trying to deploy a changeset that contains a lightning component from a dev sandbox with not much data to a partial sandbox with more data. When I go to validate the inbound changeset with settings as 'default', I get the following errors (they appear to be the same error):

Invalid definition for null:CreateSupportCaseController: null
Invalid definition for null:CreateSupportCaseController: null

My lightning component bundle contains the following:
createSupportCase.cmp createSupportCaseController.js

Is there anything wrong with the naming that could be causing the problem?

If I need to include any other information, please let me know. Thank you for the help.

enter image description here

  • It sounds like the class is failing to deploy for whatever reason. Try deploying them as two change sets, first the classes, then the bundle. Afterwards, consider logging a case with support, because I'm pretty sure we've never had this problem. – sfdcfox Aug 15 '17 at 21:48
  • @sfdcfox tried deploying separately and same error. I will log a case. Thanks. – Chase Klingel Aug 15 '17 at 22:04
  • You can actually create lightning components directly in production. Just make the classes and copy the elements over manually. – Caspar Harmer Aug 15 '17 at 22:05
  • @CasparHarmer nice idea! Could there be any repercussions to doing this? – Chase Klingel Aug 15 '17 at 22:08
  • Nope, I've done it before with no problems – Caspar Harmer Aug 15 '17 at 22:08

Try creating the component directly in production.

Just make it exactly the same name and copy the helper and controller etc files in one by one in the Developer console.

I've just verified that this works and that the component is valid - it is.

From there, the component should update properly from any updates from the sandbox, as long as the names are an exact match.

Note this only applies to the Lightning Components

Apex Classes must be deployed normally. If you have a dependency in the Lightning component to the Apex class, you can remove it and then add it back once your have successfully deployed the Apex Class.

Also consider renaming your component - Having components and apex classes that are an exact match seems like a bad idea


It seems like you don't have my domain enabled in your production org.

Activate it and try again.


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.