-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Datasource Exception while pushing Experience bundle to scratch org created from snapshot #2807
Comments
Hello @ashutrix03 👋 It looks like you didn't include the full Salesforce CLI version information in your issue. A few more things to check:
Thank you! |
Thank you for filing this issue. We appreciate your feedback and will review the issue as soon as possible. Remember, however, that GitHub isn't a mechanism for receiving support under any agreement or SLA. If you require immediate assistance, contact Salesforce Customer Support. |
Hi @ashutrix03 can you append |
@WillieRuemmele attaching the log file |
@WillieRuemmele - Did you get a chance to check the log? Do you have any update on the issue? |
@ashutrix03 - beginning to look now, can you please provide the version information requested. If you're not on |
@WillieRuemmele Here is the output of Version command. Today also I updated to latest cli version but again same error. last week I did the same. We are using codebuilder. { |
@ashutrix03 - this will take me a while to get the required orgs, metadata, etc. Can you try something for me? In step 4, create a scratch org from the snapshot, but without a namespace. I have a hunch that the ExperienceBundle in your local project requires namespace information that it doesn't have, and thus why the org can't resolve the "fullName to ID" |
@WillieRuemmele I did try creating a scratch org without namespace and I was able to deploy the community folder. The problem is unfortunately our code has namespace references in the source code hence creating a scratch org with namespace is needed. One more thing we removed any dependency on namespace from experience bundle folder |
After reading quite a bit about the ExperienceBundle type, and how it inherits fullName from the default If you want, you could verify this.
|
After following the steps that you mentioned now I am getting these errors Component Failures [4]| Type Name Problem Line:Column In the package.xml I added namespace to the EB fullname |
This issue has been linked to a new work item: W-15481620 |
hey @ashutrix03 I was looking at a similar GH issue around namespaces and found a workaround that might work here as well |
@WillieRuemmele - Any update on the Work Item [W-15481620]??(https://gus.lightning.force.com/lightning/r/ADM_Work__c/a07EE00001oMsuDYAS/view) |
Hey @ashutrix03 - did you look at using string replacements? #1803 (comment) |
@WillieRuemmele Is this issue fixed? Just now saw you marked it as completed. |
@ashutrix03 - I closed it due to inactivity, have you seen my previous comments/suggestions? |
@WillieRuemmele I did. We are going to try it this week and get back to you with the observation. Do you have any update on the work order raised? |
Oh that sounds great - it was in |
Summary
We are using Org Shape, to get all licenses from production, and Org Snapshot
We created a snapshot from a non-namespace scratch org which was created from org shape. From the snapshot we created a new namespace scratch org. We got all objects and data in this scratch. Now when we try to push Experience Bundle folder into this namespace scratch, created from a snapshot, we are getting error
We are using Code Builder to push the code into the scratch org
Error - MEP_Portal1 data.api.DataSourceException: Could not resolve fullName to ID
Steps To Reproduce
1 - Create a Org Shape
2 - Create a non namespace scratch org, we pushed objects and fields and created some data.
3 - Create a Org Snapshot from the scratch org in Step 2
4 - Create a namespace scratch org from Snapshot
5 - Try to deploy Experience Bundle in the scratch org created in Step 4. Before pushing enable "Enable ExperienceBundle Metadata API" in Digital Experience --> Settings
You will get the error "MEP_Portal1 data.api.DataSourceException: Could not resolve fullName to ID"
No one has clue what this error is about. It has been more than 1 month the case is still open with SF support and they were not even able to get anything significant from their backend logs.
Expected result
Experience bundle should get deployed
Actual result
Error - MEP_Portal1 data.api.DataSourceException: Could not resolve fullName to ID
System Information
Code Builder or VS Code
PASTE_VERSION_OUTPUT_HERE
Additional information
We are using latest version of SFDX CLI
The text was updated successfully, but these errors were encountered: