Salesforce IdeaExchange
Export Data of Recycle Bin by DATALOADER
I want to export data of recycle bin by dataloader.
"Where is this used?" button for all fields
We should have an easily accessible method if finding where any field is being used, such as via the "Where is this used" button available on S-Controls. For example, this would show
- page layouts
- formulas
- validation rules
- workflow
Custom Schedule Object
Create the ability for admin to create an object type called Schedule. Everyone can use schedules for all kinds of objects. It is impossible to create schedule with separate lines of data records and easily manipulate them and see that collection of data as a whole. Reports are good to view but the realistic use of the data is not. The same setup of the Opportunity Products schedule could be used as the model for the custom schedule. Companies are all about planning ahead and making those decisions based on a collective whole, therefore schedules can fulfill this need in looking at data.
A custom schedule would come preloaded with certain fields and a schedule similar to Opportunity Product Schedule. It would come with quantity for the number of lines, line descriptions, either date/month for each line or ability to create auto-numbering, and amount.
This could then be related to any custom object and allow for items such as revenue forecasting in other custom objects, product listing, pretty much anything that needs scheduling and not a full on task to schedule. Something that may also help is simply by adding in + at the bottom to allow addition of rows.
Ability to save 'field maps' when using data 'import wizard'
Please, please, please provide the ability to save 'field maps' when using the data 'import wizard' in precisely the same way that sdl files can be created to record mapping information when using the Data Loader.
Hours can be wasted mapping and re-mapping data files with identical layouts.
Remember, there's a 50,000 record load limit, and the Data Loader doesn't apply the same data deduplication logic that the 'import wizard' does. That's why it is necessary!
You know it makes sense.
"Print Schema" and/or "Dump Schema" to document custom schema
Hi,
This idea/need is similar to "Ability to Download SF Object Schema and ERD", but the focus is on documentation, rather than database re-creation.
I need a quick way to document our customized SFDC schema. The ideal thing would be a "print schema" selection somewhere on or under the "setup" screen. Direct and PDF options would be great.
It would be nice to be able to dump to a csv as well ("Dump Schema?"), just the schema info with no data. But just printing to a PDF would be fine for now.
Thanks!
-- David.
Data Loader Update Notification!
Here is a simple one. It would be great if somewhere within the Data Loader download page it would indicate the current release.
Roll-up summary field - cases on account
We would very much like to be able to do a count of the # cases on an account. Like other rollup summary fields we might even want to have a few different aggregates so that we could differentiate a few key types of cases or time-frames as well as an overall total.
For us having a case count by contact is not as important, but for other businesses it might be. Ideally there would be the ability to do summaries of cases at both the contact and account level.
Global custom fields
It will be great if you can provide facility to create global custom fields.
We should be able to add these global fields with standard and custom objects as custom fields.
This will be helpful if we are using same field with same values (picklist and multipicklist fields) in more than one object. Currently we needs to create/update the field labels and values in all the objects separately.
Record types should be included as 18 chars in backup
All ID fields in the backup are in 18 character form, except the record type field in each csv file, which is 15 chars long. However, the ID field in RecordTypes.csv itself is 18 chars.
Perhaps it's not a big issue, but if you try to join the CSV information together (eg external analysis, or data synthesis) then you have to REMEMBER to trim the ID of the record type records.
It's just inconsistent - surely there's no reason for this.....
Use Ranges in CASE function
I know this is a long shot, but the CASE function would be much improved if we could use ranges for the Result Criteria.
CASE(MyCustomFormulaField_Number ,
1-40, "Low"
41-80, "Medium"
81-100, "High"
"No Number" )
Protection from race conditions
Updates should be (optionally) protected against race conditions.
For example, two users change the case owner to themselves; the one who hits "Save" last is now the owner, but now two people are working on the same case because they both think they own it.
The update should be protected by ensuring that what is being changed has not changed values since the time its value was displayed.
This protection can be implemented using something like "update object set attribute = <new_value> where id = <id> and attribute = <displayed_value>;" and some logic to handle cases where the object was deleted or the value was changed, etc.
The loser of the race should see a confirmation dialog telling them that the object has been changed since they started looking at it and asking what they want to do. This should be the default behavior for many objects, with options to silently discard the attempted change, silently apply the change, or display a confirmation dialog so the user will choose whether to Save or Cancel.
Apex Data Loader: "Dry Run" test mode
When running an Insert, Update, or Upsert it would be nice to be able to run the batch but not actually have it do anything but validate the data - sort of a "what if" mode. Then you could see any errors or problems ahead of a real operation, instead of having to go back through the "error*" CSV log file to figure out which records need to be repaired and retried.
Subscribe
POST IDEA