Your source data file might not be encoded properly,
from the H&T portal, Why isn’t Data Loader importing special characters?
Make any modifications to your source data file in .xls format.
In Microsoft® Excel®, save a copy of your file as a Unicode Text
Open the Unicode Text file you just saved with a text editor.
Click File | Save ...
So the way I solve file conflict scenarios if I have no control over the file naming patterns is:
Create 2 File Locations pointing to 2 seperate folders in
Setup 2 seperate File Triggered Automations, each automation pointing to 1 of the file locations.
There is the article Salesforce Bulk Data Loads and Full-Text Search Indexes by Salesforce engineering.
Strategies for Addressing Lags in Search Indexing
So how can you architect acceptable solutions that address inevitable lags in search indexing after data loads? Here are a couple of things to consider.
Disable full-text search indexing for ...
Yes, you can import records with created and last modified dates the first time. You need not to create a case with salesforce for this.
You need to enable this in Setup | Customize | User Interface | Enable "Set Audit Fields upon Record Creation" and "Update Records with Inactive Owners" User Permissions.
Please visit this link for more information :
As for the LastName being mandatory, I can only say that it's by design. And seems there were ideas to get it optional, but Salesforce doesn't have any plan to do so. So it is very unlikely we can get away with it.
As for the workaround, as you have noted you can either switch the FirstName to the LastName
I have seen people using a notion LNU which ...
If you do not have ETL tool and ordering a new fullcopy sandbox is expensive and not a viable option, then best way to do the data backup is to use Data loader will Bulk API option. I have seen that for 2 Million records it takes hardly a minute though it depends on number of fields which you are taking the backup.
Approach of Data migration and Data ...
The standard limit on inserting ContentVersion, which underlies Notes, is 200,000 per day. I suspect you've reached that limit.
Unfortunately, I am not aware of a way to view the consumption of this limit within the org. It's not available in System Overview or via the Limits API. You may need to wait a day for it to roll over.
Try using the following:
Bare in mind, that each day it will only import the file with that day's date.
Read about Import wildcards on Adam's blog: https://sprignaturemoves.com/import-wildcards/
The approach is load data as slowly as possible. If you load relatively less records (say 5k or less) the global search is available in the matter of seconds (for me, it was less than 30 seconds). So, instead of loading data in bulk we choose to load data in “Trickle Load” fashion. In a way it’s exactly opposite of bulk data loading. In Bulk ...
For your point first thats not possible. You need to first uninstall that package first.
For second point you can take a offline backup in Eclipse and then remove dependency of your Beta package and then reinstall again. And in end from backup create the fields and update the components.
But every time you try to install the package you need to run this ...
For this task, I recommend Salesforce DX. Simply export the records you want with:
sfdx force:data:tree:export -q "query" -p -u sourceOrg
This gets you a set of files (something like Accounts.json, Opportunities.json, and Opportunity.plan), which you can then import into another org:
sfdx force:data:tree:import p MyImport.plan -u destinationOrg
When importing multiple connected objects, it's critical that you retain the success files that Data Loader emits. These allow you to map from old Ids to new Ids as you're populating lookup fields in downstream objects.
For example, you'd load Accounts, and get back an Account success file. Then, in your Opportunities input file, you'd use an ...
ACT! is another CRM system (so a competitor to Salesforce) see the wikipedia article.
The documentation you've linked says that it's possible to export contact data from ACT! (as some file using a text-delimited format) and import it into Salesforce, that's all.
This indeed is something which is not enabled by default. You will need to ask Salesforce Support to allow allow blank file processing - a setting which is managed by a business rule in the backend of Marketing Cloud.
I was able to insert the Content Note through Workbench and when I queried it shows all the fields but not the Parent ID Field which means that we can't associate it with any Record via API or Dataloader.
Here is the screenshot of the workbench:
But this is having the Properties to share with People, Group when you open the record of Content Note.
I Used Data Loader to Retrieve the data from the Org and then made the changes in the CSV file. Then I tried to Change the ParentID to Contact and inserting the Note CSV in my org through Data Loader. It works fine.
I have also checked the OwnerID, It is optional if you are putting any OwnerID It will take the Owner ID as the user through which you are ...
The Data Import Wizard is governed by a few permissions. See What permissions do I need to import records? for more details, but basically, if you want to restrict all access, you can remove the "API Enabled" permission for users. This permission will also prevent users from doing pretty much anything outside of the UI, so you'll have to test it thoroughly.
You are getting this error because, you might have used the text NULL in the column mapped with the number field.
With the setting "Insert Null values" checked in data loader, you will have to leave the column empty for the field where you want NULL to be updated and data loader will null out the respective fields where the column was left blank.
Please find my answer below but note some questions which would be helpful for SFSE to know:
I assume the data set over the 5 sObjects isn't in Production
already? If the full data set is already in Production, then as long as you don't exclude the 5 sObjects in a sandbox template, you won't need to go down this exercise unless you want an 'explicit' backup ...
The key to this is the ContentDocumentLink record that is a junction between the Object (Account in your case) and the ContentDocument (which is the parent of ContentVersion). You have to reconstruct this.
ContentDocumentLink.LinkedEntityId = someAccountId in source org
ContentDocumentLink.ContentDocumentId = some ContentDocument ...
When you export a Discover report as a csv file, Discover uses double-quote as the text qualifier. In order to successfully import a file like this to a Data Extension, ensure you check the "Respect double quotes as a text delimiter" box when defining the Import Definition.
In this way, you'll see data that incorporates commas successfully import ...
So if you sent in a super simple CSV such as this:
You should be able to do this then:
List<List<String>> csvRecords = CSVReader.readIETFRFC4180CSVFile(Blob.valueOf(attachmentAbove));
System.debug(csvRecords);// This should output foo
System.debug(csvRecords);// This should output bar
It's not possible to resubscribe an opted-out contact with an import definition.
The only way this could be achieved right now seems to be an API call executed to the API of Marketing Cloud from a script activity using this endpoint: PATCH /contacts/v1/contacts
In Classic, once you click on the tab, choose the All option in the View drop down menu and click Go. If there is no All option, click Create New View, give it the name All, and save it.
In Lightning, once on the tab, click the View dropdown at the top of the tab and choose the All view. If there is no All view, click on the ⚙ (gear) icon, then click New to ...
I had the same error... It seems that SFDX tree:import is failing when field name has a number in it. Please look at this post here:
Hope it helps !
Make sure that "resolveRefs" and "saveRefs" are set to true. For you basically it should be enough to set "saveRefs" to true for litify_pm__ChildObj2__c. When sfdx cli inserts its (litify_pm__ChildObj2__) records the "saveRefs" flag tells if Ids should be cached (remembered) for use by other objects.
It is very well explained by sfdcfox at What Are ...
The HH:MM:S (Hours Minutes and Seconds) wild cards to your file naming pattern. This way it would be easier for the system to differentiate between the two files as they would have different names by virtue of been dropped at different times.
Best practice is to pass external ID's through to Marketing Cloud. As far as I know it isnt really built to handle these kind of operations, with the exception of ContactID and SubscriberID.
I can however propose two hacks.
AmpScript + SSJS
It would involve using the GUID function and combining it with an SSJS function to query the column where the GUID ...