It gives the error message:

Error saving record: [{"message":"Account: bad field names on insert/update call: Name","errorCode":"INVALID_FIELD_FOR_INSERT_UPDATE","fields":["Name"]}]

In the field overview window, a column with the field description should be added.

Note that the description fields is not readily available via the APIs you could expect.

It should be possible to optionally choose a more guided form, so the user does not need to know how to write a SOQL query.

When importing data the user must format dates, datetimes, numbers and booleans in the CSV input according to XSD standards. We should support parsing these values from formats chosen by the user.

Data export supports showing the result as either textual CSV or as a formatted table. Data import should support the same.

To fix this:

• The lightning domain should receive the session key from the salesforce domain, like how the visualforce domain does. Except we may need another solution, as the user may not nessesarily have visited the salesforce domain before visiting the lightning domain.
• The lightning domain does not support API requests, so we need to perform cross-origin requests.
• The button to open the menu should be visible in the Lightning UI.
• The Show field metadata functionality should be adapted to lightning, including both changed HTML structure and the fact that the page does not reaload between navigations.

We should have a way of filtering fields shown in the all data window based on properties of the fields. For example show all fields with updateable=true

I had to revert a change in 9885d99 since otherwise chrome would refuse to load the addon with an error message saying the version number was malformed.

When opening the data import popup, the Object selection is defaulted to Account. We should select the object dynamically based on what page the popup was opened from instead of always using Account. See also #10

It should be easier to perform a data import based on a data export. For example:

• Delete all records that match a particular SOQL query
• Copy the value of one field into another for all records matching a query
• Set a field to a static value for all records matching a query

csvSerialize uses the String.replace() function which only replaces the first occurrence.

It would be cool to syntax highlight the SOQL query input.

When a field is a roll-up summary, we should show the summarized child relationship, the summarized field, the type of roll-up and the filter.

We should detect when we have a subquery and autocomplete field names related to the sub object instead of the main object.

For example a query for accounts with open opportunities:

select Id from Account where Id in (select AccountId from Opportunity where

Here we should autocomplete Opportunity fields instead of Account fields.

In order to support both Chrome and Firefox without duplicating our code, we run all JavaScript in the content script attached to the main Salesforce page. This means that when the user navigates away from this Salesforce page, our pop-up windows (show all data, data export and data import) will not work anymore, when the JavaScript is gone. To avoid these broken windows we close all our pop-ups when the user navigates away from the parent Salesforce page. We should find a fix for this, so we don't need to close the pop-ups. This is mostly an issue for the data export and data import windows, and not so much of an issue for the show all data window. Fixing this may depend on https://bugzilla.mozilla.org/show_bug.cgi?id=792479

This info is already available in the describe result. We should show it in a useful way.

This makes it possible for a developer to cut-paste API-name easier.

At certain positions in the query we should be able to determine that a field name cannot be legal at the given position and we should autosuggest keywords instead (select, from, where, and, or, not, ...)

Show all data window shows this error message in Winter 16:

Error querying tooling particles: [{"message":"","errorCode":"UNKNOWN_EXCEPTION"}]

When a data import is finished with some errors or cancelled records, add a "retry" button that copies the output into the input to make it more discoverable that this is supported.

The ability to sort by columns would be extremely usefull in the "View all data" view.

We have unit tests now for data export. We should have it for the rest of the features.

For example to get the name and type of all fields in an org in a format that can be copied into Excel for further analysis.

Broke with commit 23af49b

In Summer 15, these errors appear:

Error getting setup links: [{"message":"When retrieving results with Metadata or FullName fields, the query qualificatio​ns must specify no more than one row for retrieval. Result size: 2000","errorCode":"MALFORMED_QUERY"}]
Error getting field descriptions: [{"message":"When retrieving results with Metadata or FullName fields, the query qualificatio​ns must specify no more than one row for retrieval. Result size: 356","errorCode":"MALFORMED_QUERY"}]

The autocomplete for the data export query currently supports autocompleting field names and picklist values. It would be nice if it could autocomplete other field values. Example:

• select Id from User where Profile.Name = ' should suggest valid profile names
• select Id from Account where RecordType.DeveloperName = ' should suggest valid record type names (possibly limited to names valid for the Account object)

Since we may need to issue an API call for each suggestion, we may require that the user actively requests the suggestions (for example by pressing Ctrl+Space).

The stop button only cancels "Queued" batches, and there may still be "Processing" batches after pressing the stop button. The UI should keep the Active state until the Processing batches are completed (or aborted, when we support that)

When importing lots of data, the browser freezes in the csvSerialize function. (5000 records, 1.9 MB CSV, Firefox 36, Intel Core i5 2540M) This function should not be the most resource intensive part of the import, so it should be possible to optimize it. I would expect csv parsing or xml construction to require more resources.

When opening the data export popup, the query input is initialized with a sample query "select Id from Account". We should select the object in this sample query dynamically instead of always using Account. For example if you are viewing an Opportunity record, the sample query should be "select Id from Opportunity".

When editing CSV column headers (field names) in the data import dialog, the tool should suggest valid field names for the columns, similar to how the data export dialog suggests valid field names for the SOQL query.

This will require performance optimization of the table view, for example by lazy displaying rows as you scroll.

We could then use a button you click to copy Excel/CSV format, so we don't have to show it in the browser, once browsers support the execCommand("copy") API, which they are currently implementing.

It should be possible to edit values in the Show all data popup to give users an easy way to edit hidden fields on a record.

(moved from the readme file to an issue)

May not be possible before https://bugzilla.mozilla.org/show_bug.cgi?id=792479 is fixed

The field name suggestions in the data export popup is shown on a single row. If there are too many fields to fit on a row, only the first fields will be visible. This is done to prevent the entire UI from flickering wildly as you type the query.

We should support a mode where all fields are shown. When in this mode, we could consider adding ", " (comma + space) after the field name when a suggestion is selected. This would enable the user to place the cursor after the "select" keyword and then choose desired columns by clicking the suggestions one by one.