The latest v3.3 release of the FuseIT SFDC Explorer is out and contains a number of new features. Just in time for Dreamforce '16.
Select a folder to monitor for changes (1). Anything that changes in that folder and is a supported metadata type is added directly to the package.
Select a folder to scan for files modified today (2). Finds any supported metadata types that were added today and adds them to the package.
Redeploy the most recent package (3). If you last deployed from a collection of selected files it will rebuild the package from those and deploy them.
SOSL query support
The SOQL Query tab now doubles as a SOSL query tab (no syntax highlighting yet). You can also export the results to a CSV or the clipboard as with SOQL.
On the code coverage tab the Percent column has some color coding to indicate if you are hitting the minimum 75% for that class. The individual selected classes is also shown plus an org wide coverage at the top.
The green double arrow to the right of the classes code coverage will attempt to find all the test cases that contribute the the coverage of that class. Then it queues those tests up to run.
Note that as of the time of writing there is a bug in the SOAP version of the Tooling API that is preventing individual line coverage results from being returned.
Apex test execution
If Max Failures is set to a number greater than -1 it will stop after the specified number of test case failures in an asynchronous run.
Individual Entity Viewer
When viewing an individual record by ID the field metadata will be used to expand the property grid and show all the accessible fields. Note that I'm seeing some oddities with the Entity Viewer and sometimes need to toggle between the Categorized and Alphabetical views to get it to render. It might just be something with my display drivers.
- Detect and highlight a "Skipped X bytes of detailed log" message in the debug log
- WSDL2Apex: Handle class name conflicts within a namespace.
- WSDL2Apex: Add warning for "INVALID_FIELD_FOR_INSERT_UPDATE - Number of parameters exceeds maximum: 32" - Include names for
elements in warnings.
- WSDL2Apex: Improve error handling if WSDL schema element is missing type attribute
- WSDL2Apex: ensure enum name starts with a letter. It is not allowed to start with the number in Apex.