yes, history cannot be created since AccountHistory, CaseHistory and ContactHistory doest't support create() operation.
See the following docs for more information.
Account History SOAP API
Contact History SOAP API
Case History SOAP API
Your best bet will to create a custom object and store history information in it.
Migrating activities is fairly trivial in most cases, since there are usually very few fields to work with.
Tasks have a status (done/not done), while events have a starting date/time and duration (or ending date/time). You should be able to identify most records from any reasonably designed system based on one of these two pieces of ...
Salesforce has a limit to the size of the attachments you can upload into Salesforce (assuming they are 'Attachments' and not Chatter Files). The limit for attachments was recently increased from 5MB to 25MB. For Salesforce Files, it is 2GB. See the below article.
There are so many guides and points to consider while doing data migration, but I shall try to keep it down to testing/validation of data migration only. If you have the full-copy sandbox that is the best thing, and you do migration on it first. Whether you do it on sandbox or production here are few points from my previous experience:
Once you save the file in excel in CSV Format, Open it in notepad and save it with encoding as UTF-8, Open it again in excel to see if character are appearing correctly. If Yes then load the file .
Assuming that dataloader is used to load this data in, then ensure that utf8 is checked within the settings
If you want to backup your data you can refer to this article. Also as I understand you will be only creating new records so you can just leave your old data there before you are ready to delete it. (running forward it is easy to delete with Data Loader from your export files as you have Ids there)
You can use Data Loader or some other tool like Talend if ...
The CreatedBy Field is a read-only field that cannot be updated via dataloader without "Set Audit Fields upon Record Creation" permissions. Previously you had to file a Case with Support to turn this permission on for a limited period of time when importing data. Without the permission enabled you won't see it mapped when using dataloader.
You no longer ...
After a bit of searching, I found the answer at this post:
Exporting Photos: How can you download all profile pictures for all users in a given SF org?
It uses a combiniation of REST and Python, but should do the trick for you.
Importing Photos: Chatter REST Api User Photo Example
Alternatively, if you have a small number of users (~100), then you may be ...
Likes on comments aren't supported in the sObject API. They're only supported in the Chatter REST API and through the ConnectApi methods in Apex. If you know the ID of the comment, you can retrieve the likes on that comment.
I tried researching the difference between the Object_feed object and the FeedItem object with little success. The one thing that did come up consistently is that the object_feed is only available for objects that you have enabled feed tracking on.
According to the following blog post, the data is captured in both the FeedItem object as well as the ...
The best way to do this would be a sandbox. I suggest a full sandbox.
Full sandboxes copy your entire production organization
and all its data, including standard and custom object records,
documents, and attachments. You can refresh a Full sandbox every 29
Unfortunately, this requires more licensing, but it is a 1 button ...
I found a way to load multi-line special character's data (say Japanese language) correctly as it was originally in their formatting. So what I have done is:
1. Uses a Data-Export feature to export all the records(having multi-line special charac) pertaining to any Standard/Custom objects with this CHECKBOX unchecked "Replace Return Carriage with Spaces".
Import2 can assist with the migration and mappings of your custom objects to standard objects. Please feel free to start a free sample here: https://www.import2.com/salesforce. Once the sample is done, we can work together to review the mappings and your final import requirements.
The connector does not create prospects retroactively. If you use the setting 'Automatically create prospects in Pardot if they are created in Salesforce', those prospects are created only after the connector is installed and this setting is enabled. This is what pardot documentation says about this:
Pardot creates a prospect when a lead or contact with ...
You won't be able to insert a FeedItem with Type TrackedChange.
The documentation states that you cannot create a FeedItem with all Type values, but only few. Below is an excerpt from the Type field's description:
The type of FeedItem. Except for ContentPost, LinkPost, and TextPost, don’t create FeedItem types directly from the API.
A FeedItem with ...
This question is broad so it will likely be closed but to give you a direction to look at:
You should look at FeedItem, FeedPost and FeedComment. This ERD will be helpful. The feeditems can also point to a ContentDocument.
An ETL tool would be helpful in this scenario. We did a similiar migration with Talend free ETL (not endorsing it, you can use anything ...
I've seen this in the past and it's usually because the service is either not started or hung.
A) If you are on Windows, start the Jitterbit service
- Open the Services console from the Administrative Tools.
- Locate the service Jitterbit Cloud Data Loader Tomcat Server.
- If the status is not "Started", then start the service.
- If the status ...
I do not believe that it is possible to migrate data into the History tables. They do not have the "createable" or "updateable" attributes that would allow you to populate them.
The reason is that they are audit tables. If you could edit your audit trail, it would not be entirely useful as an audit trail.
1.)Export the Accounts from Prod as a csv. Keep the 18char id intact
2.) Export the related records as a csv with the Account 18char id intact.
3.) Make a legacyid field on each related object making sure to mark it as an "External ID".
4.) Load Accounts.
5.) Load each object in turn referencing the prod id as the external id for the new record.
I never was able to get DataLoader to work reliably. I ended up using the excellent restforce (https://github.com/ejholmes/restforce) Ruby gem to craft a small script to upload attachments. This worked perfectly. I think my days with DataLoader are over.
client = Restforce.new :username => '',
You can use DBAamp you can easily access your Salesforce objects using SQL Select, Update, Insert and Delete statements.
Then you can automate by writing SQL scripts that will pull data from live and then insert them into a dev environment. It will use API calls and you have to make the selects or update in bulk to be efficient.
One way that might work would be to create prod_id fields that are external ids in your dev org and schedule the export to a csv file from production and then use the csv files to upsert to your dev org matching the production id to the external id fields in dev. Scheduling the upserts so the parent objects get upserted first.
Update: For a junction object ...
If you don't want to use batch classes to update your contacts, the other approach would be to use Developer console and run anonymous code snippets like below
String objectQuery = 'select X1337_Name__c from Contact';
List<Contact> updateContacts = new List<Contact>();
You can do it following these links:
Or you can use Salesforce APIs to integrate your data from your external applications to Salesforce.
I'm currently in the midst of this for an org of Account-Contact-Case-CaseComment-Task (a thankless task)
I'm planning on a specific runningUser + Data Loader + triggers as you can do several things
Preserve the system audit fields like CreatedDate and LastModifiedDate
Is partial success-enabled with a builtin retry file in the errorXXXXX.csv file
Your question is too broad.
You should import first parent records and then import the child records.
Like this sequence:
Also, rather than migrating all the data from one sandbox to other, you can think of refreshing a sandbox from the sandbox itself as long as sandbox types are same.
I will give you a short and direct answer to this.(I was only able to find it after couple of days research).
The easiest way to overcome this is
Do not setup existing Pardot instance with new SF org (ie. do not setup the connector with new SF)
Add all the prospects in Pardot to a specific list and name it accordingly
Get in touch with Pardot support and ...
Yes, there are a few different tools out there on the AppExchange and elsewhere that allow you to upload related records in a single pass. Services like Sesame Software's Relational Junction, Informatica, and Dataloader.io can do this, and have varying costs depending on how much you want to migrate. Please do appropriate research before selecting a service; ...