-
Notifications
You must be signed in to change notification settings - Fork 78
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]-Not being able to use the OR operator in the WHERE clause of an object with the flag "master": false #598
Comments
This case has been marked as 'to-be-closed', since it has no activity for the 3 days. |
Hello, I wanted to let you know that I am currently still reviewing your case and will inform you as soon as I have any updates. Thank you for your patience and understanding. Best regards. |
fix: Fixed issue of wrong query constructing #598
Hello |
This case has been marked as 'to-be-closed', since it has no activity for the 3 days. |
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. |
Describe the bug
If I try to use the OR operator in a query with the Master flag = false I'm getting this error (or similar ones):
FETCHING THE DATA (STAGE 2) ...
[15:21:04.802] PASS 1
...............
[15:21:32.637] [ERROR] Error during execution of the command:
(RecordType.name = 'CRM') OR (account__r.AccountNumber !=
^
ERROR at Row:1:Column:3300
unexpected token: OR.
[15:21:32.641] [ERROR] Execution of the command sfdmu:run has been completed. Exit code 4 (COMMAND_EXECUTION_ERROR).
[15:21:32.644] Total time elapsed: 00h 43m 04s 905ms .
I need to filter the records due to the number of records this table has. The query does not run without a filter.
To Reproduce
Add a master object (Like account)
Add a not master object (like contact)
add a where clause with an OR operator to the not master object (in this example, contact)
Run the plugin
Expected behavior
The query should work
export.json
_target.csv file.
N/A
The text was updated successfully, but these errors were encountered: