Einstein for Developers not available in sandbox

[MarkGoodspeed]

Einstein for developers was enabled in production org on 12/10/23. New Developer Sandboxes were created on 16/10 and 17/10.

These sandboxes have the option in settings for Enable Einstein for Developers (and it is enabled) however when selecting the sandbox in VSCode and/or Salesforce Code Builder Einstien for Developers is not available and/or message "you do not have permissions" is displayed.

A Developer Pro sandbox created later (14/11) does work correctly and Einstein for Developers is usable in this sandbox. A further Developer Sandbox created on the 16/11 also works and allows Einstein for Developers.

[jonifazo]

Hi @MarkGoodspeed - Thank you for this feedback. Are you now able to use the Einstein for Developers extension?

[MarkGoodspeed]

Hi Joni

It is still the case that Einstein for Developers is working in some orgs, but not in others, as described

MRG

From: Joni Fazo @.> Sent: Monday, December 4, 2023 11:01 PM To: forcedotcom/Einstein-GPT-for-Developers @.> Cc: Mark Goodspeed @.>; Mention @.> Subject: Re: [forcedotcom/Einstein-GPT-for-Developers] Einstein for Developers not available in sandbox (Issue #32)

Hi @MarkGoodspeedhttps://github.com/MarkGoodspeed - Thank you for this feedback. Are you now able to use the Einstein for Developers extension?

- Reply to this email directly, view it on GitHubhttps://github.com/forcedotcom/Einstein-GPT-for-Developers/issues/32#issuecomment-1839679395, or unsubscribehttps://github.com/notifications/unsubscribe-auth/APFSSUJO4OZ4CZQB27BMBDLYHZI2RAVCNFSM6AAAAAA7PVO2KOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZZGY3TSMZZGU. You are receiving this because you were mentioned.Message ID: @.**@.>>

[hariss63]

Any update on this issue.

I couldn't be able to use this feature as I got the below message when clicking the Einstein logo on the VS Code

"no einstein for developers permission in default org"

[smarvez]

Hi @hariss63 - We are actively looking into the issue and will let you know when we have a resolution. In the meantime, thank you for your patience!

[gbockus-sf]

Howdy! Sorry for the delay. We've been chasing this issue and think we understand it. We have planned work to address most likely closely following Dreamforce (so late Sept timeframe). In the meantime there isn't a good workaround as we're limited in what we can do with sandboxes older then when we changed how E4D uses org permissions. It basically boils down to there's no longer a UI to work with the Permission and if it was already off when the sandbox was created it can't be turned on.

We plan on resolving that by exposing the permission and making it simple to find out why E4D is disabled. We tracking this work internally and will update as it gets addressed. Thanks!