3

Implementing SFDX for some new work. Here is what I have so far, the Dev Hub is a business org, created a project, created a scratch org, retrieved a managed package via the MetadataAPI, unzipped the file, and converted it. Smooth sailing.

When pushing this into the scratch org, I am getting a dozen or so errors. Errors such as: 

"no CustomField named CustomObjectName__c.Response_text__c found" 

"Invalid definition for PackageName:LightningCmpNameComponentController: null"

I have checked that the "missing" items throwing the errors (above, the custom object/custom field, Lightning component) are included in the managed package. I am adding the temporary MetadataAPI retrieval folders at the project root, where the config/ and force-app/ directories are. As far as I can tell from the docs, this is the correct place for that to happen. Not sure what I am missing here.

Any ideas out there? They will be greatly appreciated.

Improve this question
3
  • In the business org, this package I'm trying to install is an installed package (Setup/Installed Packages) vs. appearing in the package manager (Setup/Package Manager/Packages). Not sure if this makes a difference or not.
    – Rachel Mahan
    Jan 26, 2018 at 20:13
  • UPDATE I figured out the issue! I was following the winter 18 SFDX developer guide under Project Setup: Retrieve Source from an Existing Managed Package. I was retrieving the package from the MetadataAPI, unzipping, then converting it. But, I needed to follow these instructions instead.
    – Rachel Mahan
    Jan 26, 2018 at 22:56
  • Be sure to add this as the answer below so we can vote on that. Inter 24 hours of posting your own answer you can mark your own answer as the correct one.
    – pchittum
    Jan 28, 2018 at 7:48

1 Answer 1

Reset to default
1

UPDATE:

I figured out the issue! I was following the Winter 18 SFDX Developer Guide under Project Setup: Retrieve Source from an Existing Managed Package. I was retrieving the package from the MetadataAPI, unzipping, then converting it. But, I needed to follow these install package in a target org steps instead.

If anyone would like to chime in on why the first source was not working, please share your thoughts. I am glad a solution was found, but would love a bit more understanding on this issue. Thanks!

Improve this answer

You must log in to answer this question.

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