Selecting Start Wizard will take you into Step 1 where you can add a new file to upload. Imports are automatically deleted from the wizard after 30 days. If you do not need these past imports, it is highly recommended that you delete them as their presence can skew your filter results. You will be taken into the Imports dashboard where you can start a new upload, manage import templates (if applicable with your license), start an automated import using a saved template (if applicable with your license), or go back into a prior import to complete or view the progress.Īny incomplete and/or complete imports are stored in Cloudingo and are listed in the Import dashboard. To navigate to the Import tool, click the Dashboard menu and choose 'Imports'. However, due to the technical structure, you cannot make changes to your selections from steps 1-4 once you move past those stages. As you work through each tab, you can go back to a previous tab to view your prior selections. There are six tabs/steps to cleansing and importing a file of records. If you wish to perform a scan against a CSV file to find potential matches, but you do not intend to merge or insert new records, please see more information regarding our Find Data tool here. After scanning is complete, Cloudingo will tell you which records are 'unique' (have not detected a match) and those records can then be pushed in new. You can perform as many scans against as many filters as you wish to ensure that you have found all possible matches within your org. Rules can be configured to determine if the file data will override any of the existing data once the merge is performed. You can choose to merge the file data into the existing record when a match is detected. ► Video: Import Wizard Part I - Filters & Automation RulesĬloudingo's import tool allows you to check your CSV file for existing records before bringing them into Salesforce. If you need different criteria, create new filters and rules before you start importing. The import wizard uses your existing filters and automation rules. This information is always included by Salesforce in the response when a call is made.Before you start a multi-object import, it’s important to decide how you want to find and merge duplicates. This could be for example in the Salesforce Connector, a button that allows you to see the current API Usage. There is a monthly limit to the number of calls that can be done in a Salesforce org, so it would be very useful to have an API usage counter to know the current state. Record limit: Is there a limit to the number of records that can be imported/exported? Are you always using the REST API, or do you use the BULK API for operations with a significant number of records (for example 10000 or more)?ĪPI usage: with each import/export or when loading the object/field selector, API calls are done to Salesforce in order to obtain this information. If we have a custom OAuth App and we want to use the Salesforce actions in EasyMorph, we have to add all these OAuth scopes to our custom OAuth app for it to work correctly, right? OAuth scopes: Here are the OAuth scopes that the default EasyMorph OAuth app has: If we want to keep using a “Web Location” connector to connect to Salesforce (for example, if we want to keep having a custom callback URL), why can’t we select it from this dropdown? Even though it’s a “Web Location” connector, its being used for Salesforce, so it should still work correctly right? Refresh token: does this connector automatically manage refresh tokens?Ĭonnector selection in Import/Export actions: The connector dropdown in the Import/Export action only allows to select “Salesforce” type connectors. Does the default callback URL have to be “ ”? Could this be customized? I guess that’s because the callback URL in my custom OAuth app is different to the default one in the EasyMorph connector. Could there be two buttons for authorizing: “Authorize (Production)” and “Authorize (Sandbox)”? Depending on that, the URL starts with either or .Ĭustom OAuth app: when trying to connect with a custom OAuth app, I get the following error in the browser: I’ve tried changing “login” to “test” manually in the URL that EasyMorph generates, I get to log in but the connector doesn’t get authorized. Sandbox orgs are used for testing features before moving them to production orgs, so being able to connect to a Sandbox org is important, in my opinion. I’ve been trying out the Salesforce Connector, it’s looking good!Īuthorization URL: It works with production orgs (URL for authorizing begins with, which is the case when pressing the “Authorize” button), but not with sandbox orgs (in this case, the URL for authorizing begins with ).
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |