Skip to content
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

[BUG] - Support SELECT all FROM Product2 #938

Closed
PotSeht opened this issue Nov 29, 2024 · 6 comments
Closed

[BUG] - Support SELECT all FROM Product2 #938

PotSeht opened this issue Nov 29, 2024 · 6 comments
Assignees
Labels
feature-request New feature request or a change in the existing functionality to-be-closed The issue is about to be closed

Comments

@PotSeht
Copy link

PotSeht commented Nov 29, 2024

Hi @hknokh

I am trying to migrate Product2 records from sandbox to sandbox, and am hitting the below error. The field is fine from an FLS perspective.

[12:13:36.877] [ERROR] Error during execution of the command: Recommended_Retail_Price__c, ExternalDataSource.DeveloperName ^ ERROR at Row:1:Column:3200 Didn't understand relationship 'ExternalDataSource' in field path. If you are attempting to use a custom relationship, be sure to append the '__r' after the custom relationship name. Please reference your WSDL or the describe call for the appropriate names.. [12:13:36.879] [ERROR] Execution of the command sfdmu:run has been completed. Exit code 4 (COMMAND_EXECUTION_ERROR).

I have tried using ScriptObject's excludedFields, targetting both ExternalDataSource and ExternalDataSource.DeveloperName, to no avail. The documentation for externalFields states fields specified here are excluded from the SOQL query, perhaps this is not entirely true, or possibly some kind of bug?

My Export JSON looks like this:

{
    "objects": [
        {
            "query": "SELECT all FROM Product2",
            "operation": "Upsert",
            "externalId": "Name",
            "excludedFields": ["ExternalDataSource,ExternalDataSource.DeveloperName"]
        }
    ]
}

Whilst I have a workaround, explicitly stating each and every field on Product2 which can be tedious. It would be great to investigate if this is something that could be easily rectified.

Thank you very much

@PotSeht PotSeht added the feature-request New feature request or a change in the existing functionality label Nov 29, 2024
@hknokh
Copy link
Collaborator

hknokh commented Nov 29, 2024

Hello, @PotSeht

Thank you for your feature request.
I will review it as soon as possible and provide updates as they become available.

Cheers

@hknokh2
Copy link
Contributor

hknokh2 commented Dec 1, 2024

Hello
It does not look as a FeatureRequest.
Please rename your ticket accordingly, I will take a look on it asap.
Regards.

@PotSeht PotSeht changed the title [FEATURE REQUEST] - Support SELECT all FROM Product2 [BUG] - Support SELECT all FROM Product2 Dec 1, 2024
@PotSeht
Copy link
Author

PotSeht commented Dec 1, 2024

Hello - I marked it as this as I wasnt sure whether it was truly a bug or not. I have renamed.

Thank you

@hknokh2
Copy link
Contributor

hknokh2 commented Dec 4, 2024

Hey
Perfect.
I don't currently have anough time for this now, but will see it later.
Regards

Copy link

github-actions bot commented Dec 8, 2024

This case has been marked as 'to-be-closed', since it has no activity for the 3 days.
It will be automatically closed in another 3 days of inactivity.

@github-actions github-actions bot added the to-be-closed The issue is about to be closed label Dec 8, 2024
Copy link

This case has been closed, since it has no activity for the last 6 days. Feel free to reopen it, if you need more help.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request New feature request or a change in the existing functionality to-be-closed The issue is about to be closed
Projects
None yet
Development

No branches or pull requests

3 participants