@W-16485311: Core Logic for Selecting Records from Target Org #3818
Conversation
…ing/CumulusCI into feature/select_records
…ing/CumulusCI into feature/select_records got # Please enter a commit message to explain why this merge is necessary,
…support ORDER BY operation
Also solve issue where offset if greater than 2000, was causing an issue
|
Out of curiosity, would this feature enable selects against the User object? I have a current use case for querying User records and relating them to data in a dataset using the user alias field value. It would be really cool if dataset extract could do that mapping to user alias automatically :) |
|
Hey @jlantz, This tool is primarily designed to load data into a Salesforce org, not extract it. While I'm not sure what you mean about user aliases, you can theoretically add the "User" object to the mapping file and set its action to "select." This means that when you load data into the target org, the tool will query for existing user records in the target org instead of creating new ones. It will then link these users to other objects based on lookup relationships. Hope this helps :) |
|
To further clarify, the goal is to enhance the tool by introducing a feature that allows users to select existing records in the target org. This would provide a way to reference these existing records when creating related child entities during the data load process. |
| import numpy as np | ||
| import pandas as pd | ||
| from annoy import AnnoyIndex | ||
| from sklearn.feature_extraction.text import HashingVectorizer | ||
| from sklearn.preprocessing import StandardScaler |
There was a problem hiding this comment.
Hey @mjawadtp, I guess we need to also make changes in the requirements/dev.txt and requirements/prod.txt files to include these new imports.
There was a problem hiding this comment.
Discuss with James
W-16485311
Select_Operation.mp4