Data.com fields required in Sandbox.

[trailheadapps]

Data.com fields required in Sandbox.

[github-actions]

Welcome! 👋

Thank you for posting this issue. 🙇🏼‍♂️ We will come back to you latest within the next 48h (working days). Stay tuned!

[aaronmattern]

I removed the reference to these fields, as well as. Not sure why my org doesn't have them. Finally got the package installed via CLI.

Account.DunsNumber
Account.NaicsCode
Account.NaicsDesc
Account.OperatingHoursId
Account.TradeStyle
Account.YearStarted

[guivlm]

I removed the reference to these fields, as well as. Not sure why my org doesn't have them. Finally got the package installed via CLI.

Account.DunsNumber
Account.NaicsCode
Account.NaicsDesc
Account.OperatingHoursId
Account.TradeStyle
Account.YearStarted

How have you removed that @aaronmattern? Having the error message as you faced installing via package.

[aaronmattern]

@guivlm

Yes, this allowed me to at least deploy the package into my sandbox.

However,when I launch the app I'm getting another error:
Regex too complicated

[guivlm]

@guivlm

Yes, this allowed me to at least deploy the package into my sandbox.

However, when I launch the app I'm getting another error:
Regex too complicated

@aaronmattern Thank you for helping me with the deploy. It worked.
Now I'm facing the same issue as you.

This might be related to the class RecipeTreeViewController and the following governor limit:
https://help.salesforce.com/articleView?id=000325937&language=en_US&type=1&mode=1

[codefriar]

@aaronmattern @guivlm,

Are both of you installing this into an otherwise pre-populated sandbox?

A little bit of background:
Apex Recipes only really ships the actual .cls files. The UI components here interact with those classes generating the Docs, and groupings from the doc blocks in the code itself.

The RecipeTreeViewController is currently scoped to populate the tree view with all the apex classes available in the org that do not match our test class naming convention. If you have a bunch of other classes in the org, or you do not follow our test class naming convention, then this can happen.

In the near term, I suggest you use Apex Recipes in a net-new Dev org, or Scratch org.
In the longer term, I'm looking at namespacing the Apex Recipes classes so this doesn't happen.

[aaronmattern]

Yeah, I was trying to use it in a dev sandbox of my company. I'll try it in a scratch org, dev org, or playground in the future.

[codefriar]

@aaronmattern - I've a PR in to fix this, but I still recommend you using a dedicated scratch org for this.