Updates to data entry grid

We've updated the grids where users enter data for direct entry indicators. These new grids look a little different, but more importantly, this allowed us to fix in place the column headings and row labels. Now, if you need to scroll through a big table, you'll always know what cell you're editing.

GIF shows column headings and row labels fixed in place as someone uses horizontal and vertical scroll.

Along with this update, we've separated the indicator Targets & Data tab into two tabs… Targets and Data. The targets are in the targets tab, and you can probably guess the rest.

Image shows the old version of indicator page options with "Targets & Data" as one tab, plus the new version with separate "Targets" and "Data" tabs.

Other changes you might notice: The comments field in data entry grids is a little different and you can now use the tab key to quickly move between cells.

Image shows editable grid with a blue-bordered comments box when user has clicked on a comments cell to edit.

Templates for importing program info

For those responsible for adding new program info to your DevResults site: Today we have a huge update that will make your life easier. All the major index pages in DevResults now have a Download Blank Template option. This will give you an Excel template for adding activities, indicators, organizations, users, or locations. You can find this option in the gear menu on any of these index pages.


The templates only include fields that can be edited via import, so you can fill out whatever columns you'd like and then upload it to DevResults.


In the future we will add built-in drop-downs for fields with a defined set of options, like an indicator's data source, but all templates are currently validated upon import.

Simplified Mechanisms

Today we've released an update to simplify the Mechanisms page. Mechanisms let you identify what kind of funding is received by your activities (or whatever you call them).

Previously, we offered a system with mechanism sub-types (like "Fixed Price") that each belonged to a type (like "Contract"). Activities were then identified with the Type (Sub-Type) pattern, such as "Contract (Fixed Price)".


These options were more complex than useful, so we got rid of them in favor of a simple list of mechanisms. This brings mechanisms inline with how we manage other category options like sectors and tags.


Your mechanisms table now shows the Type (Sub-Type) pattern. If the type matched the sub-type (like "Purchase Order" in this example), it's listed as-is. This matches the way mechanisms were already displayed for activities, so no changes have been made to how your mechanisms look and no action is required on your part.


IATI Hub: support added for 'Target Groups' description

Small update to IATI activity file exports — the Beneficiary Description field on the Activity Overview tab will now be published as the IATI "Target Groups" description. This is in addition to the preexisting support for Context and Objectives fields publishing as "General" and "Objectives" descriptions respectively.

Publishers are encouraged to publish all three IATI description types, but at least one is required to generate an export from DevResults.

New download options for narrative responses

Users can now download all narrative questions and responses for all activities in a single reporting period, as well as for a single activity reporting period. Previously, this was only available as a custom query.

To download all responses for a single reporting period, click on the gear icon for that reporting period, and select "Donwnload narrative responses".


To do so for a single activity, click on the gear icon in the Activity Reporting Period and select "Download narrative responses".


IATI Hub: support added for <humanitarian-scope>

Just in time for new guidance on publishing IATI data on the Covid-19 response, we've added support for the <humanitarian-scope> element and its associated codelists to classify emergencies, appeals, and other humanitarian events or actions.

To start using humanitarian scopes, first be sure that you or your site owner has added the relevant codelists on the IATI Hub Settings tab. codelists.png

To add a humanitarian scope to an activity, go to the IATI tab for that Activity and click on the "Add a humanitarian scope" button — this will reveal a dropdown to select a scope type (emergency or appeal). The scope vocabulary can then be selected from a dropdown in the table. The scope code and narrative are free text fields, however, and will require copying and pasting the relevant codes/names from the GLIDEnumber (secondary source) and Humanitarian Response Plan databases themselves.


Permissions for editing an activity are now more consistent

DevResults' permissions are based on concepts rather than pages or menu items. And the concept of an activity could be described as "part of an organization that reports certain indicators, at certain times, in certain places."

Logically, editing an activity includes assigning each of these four components. We recently discovered that users with View & Edit permissions for activities were only able to assign indicators — not the other three.

This update ensures that users with View & Edit permissions for activities can assign indicators, organizations/users, reporting periods, and geographies to activities.

Importantly, enabling someone to assign any of these components to an activity does not allow them to edit the definitions of those things. User groups can be prevented from making changes to indicator definitions, organizations, users, reporting periods, or geographies by enabling only View permissions for those components.

Permissions settings example

"Geographic Disaggregation" replaces "Reporting Level"

For many years, we've explained that an indicator's reporting level is its geographic disaggregation. So why not just call it that?

Now we have.


Throughout DevResults, we've replaced the term Reporting Level with Geographic Disaggregation.

Better yes/no display in data tables

We've made a very small (but hopefully very useful!) tweak to how Yes/No data displays in data tables. Previously, the difference between "No data" and "No" wasn't immediately obvious to new users. We've updated the display to add text and improved the icons used so the distinction is clearer for all users.



New Dashboard Tile: Progress to Global Target

DevResults is proud to announce the release of a brand new dashboard tile! The Progress to Global Target tile displays icons for your choice of indicators to show how well you're doing against your targets.


The left-hand configuration panel lets you 1) select indicators to include, 2) choose and the relevant reporting periods, and 3) display the data for either just one reporting period (incremental) or all data up to that point (cumulative).


The parameters for this tile are defined in each indicator's Targets & Data tab. You can set the Progress Interpretation (either higher or lower is better) and define the ranges that show a progress icon for Good (green), Warning (yellow), or Bad (red). A grey square appears on the tile if there are no targets for that reporting period. By default, indicators are defined as higher is better, with good as ≥100%, and bad as <100%, but you can add a warning and set each to whatever you'd like.


Because this tile shows global targets and data across all activities, it is not available to partners. We have future plans for a Progress to Activity Target tile, though!

Learn more about the Progress to Global Target tile in our knowledge base.