Help get this topic noticed by sharing it on Twitter, Facebook, or email.

SalesForce Audit Columns

We have asked SalesForce to open up the Audit Columns for us to do a conversion. DBAmp still sees them as not creatable/updateable, but when using the DataLoader we were successful in loading data. Is there something that needs to be done to allow DBAmp to create the audit columns?
Checking the sys_sffields table:
ObjectName Name Type Label SQLDefinition Calculated Createable DefaultedOnCreate Filterable NameField Nillable Sortable Unique Updateable AutoNumber RestrictedPicklist ExternalID RelationshipName
Premium_Transaction__c Certificate__c boolean Certificate varchar(5) not null false true true true false false true false true false false false
Premium_Transaction__c CreatedById reference Created By ID nchar(18) null false false true true false false true false false false false false CreatedBy
Premium_Transaction__c CreatedDate datetime Created Date datetime not null false false true true false false true false false false false false
1 person has
this question
+1
Reply
  • are you using the exact same sf user on the linked server as you are with the data loader?

    also, are you able to update those fields inspite of the sffields info !
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly indifferent, undecided, unconcerned happy, confident, thankful, excited sad, anxious, confused, frustrated

  • No, it was not the exact user, the DataLoaded user happened to be a SysAdmin. We updated our DBAmp user to SysAdmin, and was able to Insert the Audit Columns. We've gone back to SalesForce again, but this may be our workaround during our conversion.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly happy, confident, thankful, excited sad, anxious, confused, frustrated indifferent, undecided, unconcerned

  • Hi Bill, been testing the MigrateAmp, so far so good, EXCEPT...

    We are having issues with the Audit Fields again, when creating a Campaign and CampaignMember, the CreatedDate/CreatedBy columns are defaulting to the DBAmp User and current DateTime. However when SF_BulkpOps does Lead, it inserts it correctly.

    Doing the same Campaign / CampaignMember with DataLoader correctly does the
    original CreatedDate/CreatedBy values.

    Any suggestions on what might be causing the issue, or what to look for?
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly happy, confident, thankful, excited sad, anxious, confused, frustrated indifferent, undecided, unconcerned

  • Should have added, we were using the same user for both DBAmp and DataLoader.

    In Addition, we did update the user to a SysAdmin to try and see if that
    worked. It did not make a difference.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly indifferent, undecided, unconcerned happy, confident, thankful, excited sad, anxious, confused, frustrated

  • Can you post the sf_bulkops output from the Insert into Campaign ? This output will be somewhere in the message output of the _Load proc. I'd like to see the messages starting with the "Starting SF_Bulkops" line.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly indifferent, undecided, unconcerned happy, confident, thankful, excited sad, anxious, confused, frustrated

  • Here is the Campaign Load, as you can see we got the warning:
    --- Starting SF_BulkOps for Campaign_Load_usp_MigrateCampaignMember V3.1.7
    10:33:12: Run the DBAmp.exe program.
    10:33:12: DBAmp Bulk Operations. V3.1.7 (c) Copyright 2006-2016 forceAmp.com LLC
    10:33:13: Inserting Campaign_Load_usp_MigrateCampaignMember (OOCSVODDB001V\DBAMPDEV / SalesForceDataMart).
    10:33:13: DBAmp is using the SQL Native Client.
    10:33:14: Warning: BulkAPI operations without a Sort column could perform slowly.
    10:33:15: SF_Bulkops will poll every 60 seconds for up to 3600 seconds.
    10:33:15: Warning: Column 'AmountAllOpportunities' ignored because it not insertable in the Campaign object.
    10:33:15: Warning: Column 'AmountWonOpportunities' ignored because it not insertable in the Campaign object.
    10:33:15: Warning: Column 'Analytic_Snapshot_Total_Leads__c' ignored because it not insertable in the Campaign object.
    10:33:15: Warning: Column 'AssignmentGroupActiveAgents__c' ignored because it not insertable in the Campaign object.
    10:33:15: Warning: Column 'Campaign_ROI__c' ignored because it not insertable in the Campaign object.
    10:33:15: Warning: Column 'CaseSafeID__c' ignored because it not insertable in the Campaign object.
    10:33:15: Warning: Column 'CountPremiumsonCampaign__c' ignored because it not insertable in the Campaign object.
    10:33:15: Warning: Column 'CountPropertiesonCampaign__c' ignored because it not insertable in the Campaign object.
    10:33:15: Warning: Column 'CountRequiredPremiumsonCampaign__c' ignored because it not insertable in the Campaign object.
    10:33:15: Warning: Column 'CountResortsonCampaign__c' ignored because it not insertable in the Campaign object.
    10:33:15: Warning: Column 'CreatedById' ignored because it not insertable in the Campaign object.
    10:33:15: Warning: Column 'CreatedDate' ignored because it not insertable in the Campaign object.

    Here is the Campaign Member, we DID NOT get the warning:
    --- Starting SF_BulkOps for CampaignMember_Load_usp_MigrateCampaignMember V3.1.7
    10:33:40: Run the DBAmp.exe program.
    10:33:40: DBAmp Bulk Operations. V3.1.7 (c) Copyright 2006-2016 forceAmp.com LLC
    10:33:40: Inserting CampaignMember_Load_usp_MigrateCampaignMember (OOCSVODDB001V\DBAMPDEV / SalesForceDataMart).
    10:33:42: DBAmp is using the SQL Native Client.
    10:33:43: Warning: BulkAPI operations without a Sort column could perform slowly.
    10:33:43: SF_Bulkops will poll every 60 seconds for up to 3600 seconds.
    10:33:43: Warning: Column 'AccountID__c' ignored because it not insertable in the CampaignMember object.
    10:33:43: Warning: Column 'AccountSpouseName__c' ignored because it not insertable in the CampaignMember object.
    10:33:43: Warning: Column 'CampaignName__c' ignored because it not insertable in the CampaignMember object.
    10:33:43: Warning: Column 'CustomerCreatedDateFormula__c' ignored because it does not exist in the CampaignMember object.
    10:33:43: Warning: Column 'CustomerRecordTypeFormula__c' ignored because it does not exist in the CampaignMember object.
    10:33:43: Warning: Column 'ExternalCampaignMemberId__c' ignored because it not insertable in the CampaignMember object.
    10:33:43: Warning: Column 'FirstRespondedDate' ignored because it not insertable in the CampaignMember object.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly happy, confident, thankful, excited sad, anxious, confused, frustrated indifferent, undecided, unconcerned

  • For some reason, the salesforce api told us that we cannot insert into that table.

    I would suggest trying a 1 row test case with the salesforce loader into Campaign. My guess is that you will get the same error message and then you could file a case with salesforce asking them to turn it on for that object as well.

    If the data loader is able to insert into those fields, let me know.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly indifferent, undecided, unconcerned happy, confident, thankful, excited sad, anxious, confused, frustrated

  • So back to the issue with CampaignMember working with DataLoader and not via DBAmp? As you can see, no warning there, but data was not inserted with data.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly indifferent, undecided, unconcerned happy, confident, thankful, excited sad, anxious, confused, frustrated

  • Are you positive that the exact same sf user was used by the linked server and the data loader ? Also, was the bulkapi switch turned off when you did the data loader test ?
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly happy, confident, thankful, excited sad, anxious, confused, frustrated indifferent, undecided, unconcerned

  • Can you post the entire output of the campaignMember insert ? We think all the records are probably failing due to a lack of contacted or leadid.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly happy, confident, thankful, excited sad, anxious, confused, frustrated indifferent, undecided, unconcerned

  • We have figured out the issue, it was related to some process in SalesForce and the order that we were processing data.

    We are still researching what trigger/process fired in SalesForce, but what happened is that the Campaign was created, then we created the Lead, this caused a CampaignMember to be created, but then when the process ran to create the CampaignMember, it was already there, but the error returned was confusing and not showing a message that indicated that was the problem.

    Not sure it this is something to consider in MigrateAmp, but I think it is an order to process the load of data issue.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly indifferent, undecided, unconcerned happy, confident, thankful, excited sad, anxious, confused, frustrated