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

Entity type ManagedContentInfo does not support query. #491

Closed
JaniszewskiMarcin opened this issue Aug 18, 2022 · 3 comments
Closed

Entity type ManagedContentInfo does not support query. #491

JaniszewskiMarcin opened this issue Aug 18, 2022 · 3 comments
Assignees
Labels
completed The issue was successfully resolved/Feature is completed feature-request New feature request or a change in the existing functionality

Comments

@JaniszewskiMarcin
Copy link

Hi,
So when retrieving data from target I have error like this. I see that this object can does not support query but how I can exclude it from the process? I deleted it from export.json and CSV files because I am using SFDMU with CSV records import to target org. Is there any workaround?

{ManagedContentInfo} Retrieving the TARGET data from Org (STAGE 2: all records) ...
Command in progress ...... done
[ERROR] Error during execution of the command: entity type ManagedContentInfo does not support query.
Execution of the command sfdmu:run has been finished. Exit code 4 (COMMAND_EXECUTION_ERROR).
@JaniszewskiMarcin JaniszewskiMarcin added the help-wanted User need a help or something not working, not a bug label Aug 18, 2022
@hknokh
Copy link
Collaborator

hknokh commented Aug 18, 2022

To exclude object from the process, use excluded = true with the object definition.
Please, refer here:
https://help.sfdmu.com/full-documentation/configuration-and-running/full-exportjson-format

@hknokh hknokh closed this as completed Aug 18, 2022
@hknokh hknokh added the completed The issue was successfully resolved/Feature is completed label Aug 18, 2022
@JaniszewskiMarcin
Copy link
Author

JaniszewskiMarcin commented Aug 23, 2022

Hello @hknokh I tried this but still getting same error:

		{
			"query": "SELECT all FROM ManagedContentInfo",
			"operation": "Upsert",
			"externalId": "Id",
			"excluded": true
		},

@hknokh hknokh reopened this Sep 15, 2022
@hknokh hknokh added in-progress Issue is currently in the resolution progress and removed completed The issue was successfully resolved/Feature is completed labels Sep 15, 2022
hknokh added a commit that referenced this issue Oct 1, 2022
hknokh added a commit that referenced this issue Oct 1, 2022
hknokh added a commit that referenced this issue Oct 1, 2022
fix: added excludedObjects
@hknokh
Copy link
Collaborator

hknokh commented Oct 1, 2022

Hey @JaniszewskiMarcin
I've fixed the issue with the excluded objects.
You can now exclude ManagedContentInfo in two ways:

  1. In a "normal way": using "excluded": true in the object definition (this should work now as expected):
    {
    objects: [
    {
    "query": "SELECT Id FROM ManagedContentInfo",
    "excluded": true
    }
    ]
    }
  2. The alternative way: I've added the completely new property to the script definition to exclude list of sobjects globally across all objectSets:
    {
    "objects" : [],
    "excludedObjects": [
    "ManagedContentInfo"
    ]
    }
    Here you don't need to add ManagedContentInfo into the objects section.

Please update the plugin and let me know how it's working for you.

@hknokh hknokh added feature-request New feature request or a change in the existing functionality completed The issue was successfully resolved/Feature is completed kb Need to put it to the Knowledge Base and removed in-progress Issue is currently in the resolution progress kb Need to put it to the Knowledge Base labels Oct 1, 2022
@hknokh hknokh closed this as completed Oct 10, 2022
@hknokh hknokh removed the help-wanted User need a help or something not working, not a bug label Dec 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
completed The issue was successfully resolved/Feature is completed feature-request New feature request or a change in the existing functionality
Projects
None yet
Development

No branches or pull requests

2 participants