Over time, I could see this becoming a growing issue as multiple people move from company to company that all use Salesforce?
We are looking to provide more complete undo functionality in a future roadmap.
Is there any downside to my making Job_Application__c a junction created with lookups rather than M-D's? Or could I make it M-D on one of the relationships? (Probably to Position, since if you delete a position, all of it's applications probably can be deleted as well..)
You can require the relationships on the page layout for the lookups, which will work roughly the same for users. In terms of cascade delete, you can probably do one relationship master detail to allow that functionality, but it would be good practice to have some sort of apex trigger or declarative automation to delete orphan records.
You don’t have permission to access these fields on ContentVersion. Ask your Salesforce admin for help.
Why is this? Is this the best tool to move all the Documents over? I understand that to prepare for Lighting Covnersion, Documents is something that doesn't exist so it's best if I move these. But what's the best and easiest way?
Assign the Attachments and Notes Migrator Permission Set to Admins
1. From Setup, enter Permission Sets in the Quick Find box, then select Permission Sets.
2. Select the recently added permission set Attachments and Notes Migrator - Admin.
3. Select System Permissions.
4. Click Edit and enable the following permissions:
In the Systems section:
a. Modify All Data
b. Set Audit Fields upon Record Creation
In the Users section:
c. View All Users
5. Click Save.
6. Click Manage Assignments.
7. Assign the permission set to anyone who will be using this tool to migrate attachments or notes.
This typically includes admins.
The Omni-Channel utility appears in the utility bar in your Lightning Console app. From there, agents can change their presence status and triage their incoming work assignments.
From Setup in Lightning Experience, enter Apps in the Quick Find box, then select App Manager.
Click the dropdown next to the console app your want to add Omni-Channel to, then click Edit.
Under Utility Bar, click Add.
Is 'Field_name_1__c' blank?
Yes - Check if 'Field_name_2__c' is blank (see below)
No - return 'Yes'
Is 'Field_name_2__c' blank?
Yes - return 'Pending'
No - return 'No'
Any ideas? I presume it would be an IF Formula but I'm unsure how to do this.
Multi-picklist field: Marketing_Promotion_Code__c
Single picklist field: ChannelRequestType__c
When either or both of these values are selected in the mulit-picklist field: 6TO-FY14-LTD, 8TO-FY14-LTD. The following picklist value: "Marketing Promo" is required to be entered in the "Channel Request Type" field.
I am not sure how to write this validation rule because I keep recieving syntax error: Multi-select picklist fields are only supported in certain functions.
You didn't need the TEXT as ISBLANK works with multi-select fields. Also you didn't need the OR() because you were only checking ChannelRequestType for 1 value rather than 2 values.
Then I export all the users to a CSV file, and move the user ID column to the last column, instead of the first (for the next step)
Then I use a VLOOKUP to pull in the correct User ID to the first CSV file, using whatever criteria needed. (match on email address, for example). Overwrite the existing values in the OwnerID column, or add one with that name if you didn't export it.
Then you just pass the CSV file to the data loader, and choose which fields to map (in this case, you just need ID and OwnerID)