Nfield update

After a thorough review, we found that the Nfield Composer is not actively being used by our customers. Since maintaining this tool comes with ongoing Azure hosting and development costs, we have decided it is no longer practical to continue supporting it.

We have therefore made the decision to officially deprecate the Nfield Composer.

At the same time, we want to assure you that we are committed to providing better tools for your development needs. We are currently working on a new feature called the Online Developer, which will be fully integrated into the Nfield Manager.

This new Developer is designed to be more visual, intuitive, and user-friendly, offering an improved experience for creating and managing surveys within Nfield Manager. We will announce the timeline for this new feature once we are closer to its rollout. Currently, it is still in the early stages of development.

We recommend customers to stop using the Composer as soon as possible, as starting the week of August 18, 2025, you will no longer be able to create Composer scripts in Nfield. After this date, Composer will be fully deprecated.

On the 1st of July video playback stopped working in NfieldChicago. It was found that NfieldChicago relied on an outdated version of Azure Media Player.

We have fixed this issue by implementing a different media player. The updated NfieldChicago template has already been deployed everywhere. We have confirmed that video playback again works as expected, with the following *UIOPTIONS:
- media
- media-content-type
- media-poster
- autoplay
- media-width
- media-height
- minimum-duration
- minimum-duration-message

Although Nfield allowed it, *ROT and *RANDOM did not work on questions with *DUMMY. With the next release will make it work. This allows you to randomize or rotate a dummy question and use it as target on other questions through *ORDER QnR. You would no longer have to write a custom ordering to randomize multiple questions.

Example:

*template NfieldChicago

*QUESTION 100 *CODES 61L5 *ID MainSortList *RANDOM *DUMMY
You should not be able to see this
1:a
2:b
3:c
4:d
5:e

*QUESTION 1 *CODES 71L1 *ID useletters 
Do you use letters?
1:yes
2:no *goto {AwareLetter}

*QUESTION 2 *CODES 72L2 *ID FavLetter *ORDER Q{MainSortList}R 
What is you favourite letter?
1:a 
2:b 
3:c
4:d
5:e

*QUESTION 3 *CODES 74L5 *MULTI *ID "AwareLetter" *ORDER Q{MainSortList}R *CONTROL Q{FavLetter} N
Which of these letter have you heard of, if only by name?
1:a
2:b
3:c
4:d
5:e

In the next Nfield release, we will be implementing some changes to the v2/Token/Refresh endpoint. In order to enhance security and prevent token theft, we are adding DPoP (Demonstrating Proof of Possession) as an extra layer of protection.

From the next release onwards, if you want to make use of refresh tokens, you will be required to add a DPoP header in the requests for both the access token (v2/Token endpoint) and the refresh token (v2/Token/Refresh endpoint).

This has to be configured on the client-side so you will have to make the necessary adjustments, if you wish to use the v2/Token/Refresh endpoint going forward. Recent usage metrics indicate this should not have a significant impact on clients. If you are not using refresh tokens, no changes are required at this stage.

With the next Nfield release, we will also be releasing an updated version of the Nfield Public SDK, which contains examples of how this could be implemented.

Our long-term aim is to require DPoP throughout the entire Nfield Public API, but we will inform you ahead of time of any further changes which may be required.

From 1 September 2025 onwards the minimum version of the Nfield CAPI app that can be used for fieldwork is 2.32. Interviewing devices that are running a version of the app that is lower than 2.32 will no longer be able to synchronize with Nfield.

As a Domain Administrator it is important to share this news within your organization so it gets the attention of the people that should act. If you are working with the older Nfield CAPI app versions that stop being supported, now is the time to ensure business continuity by keeping your CAPI devices updated with at least the minimum required app version (preferably upgrading them to the latest CAPI app version).

NIPO will raise the minimum supported Android version to Android 13 on 1 September 2025.

What does this minimum supported version mean for you? If you encounter a problem with your device, for instance, an issue with performance, and the device is running an Android version below the minimum supported version, we will always first ask you to upgrade to at least the minimum supported Android version. It also means that all future releases of the Nfield CAPI app will require at least the minimum supported Android version to be installed on your device.

As a general recommendation we advise you to update to the latest Android version on your device(s) as soon as you can.

As always, please share this information with all relevant people in your organization.

© NIPO 2025
NIPO, Amsteldijk 166, 1079 LH, Amsterdam, The Netherlands  

Archive of Nfield (e)mailings | Contact us