Custom fields missing

A fix for this issue has been implemented in version 2025.3.100
Implemented Backlog

Custom fields missing

avatar

We use custom fields a lot in our instance, but we can no longer add or edit them. The interface seems to be gone for new entries. I can edit older entries (called "Website (verouderd)") and there the interface for managing custom fields is still there. How can we add/ edit/ delete custom fields in the new interface?

All Comments (9)

avatar

Also, it no longer seems to be possible to add/edit OTP keys?

avatar

Never mind the OTP part, that's simply renamed. :) Leaving me with the issue of the custom fields

avatar

Hello,

Thank you for reaching out on this matter.

I was able to reproduce the issue you are experiencing with the custom field in Hub business. I will report this bug to the development team, and they will begin working on a fix soon.

I will follow up with you as soon as a fix is deployed in a future update.

Best regards,

Jacob Lafrenière

avatar

Here is some additional info:

This is the new layout (missing custom fields)

Vs the old layout (with Aangepast velden - or custom fields):

41fed763-d328-445e-8e4e-f2bead7be646.png

e0737251-4230-4874-8643-c65f8bb2c0e5.png

avatar

Hello,

Thank you for the additional information.

I’ve added the details you shared to our internal case related to this issue. Our development team is currently working on resolving it.
I will follow up with you as soon as a fix is deployed in a future update.

Best regards,

Jacob Lafrenière

avatar

We also notice the same issue. Custom fields is missing for Website

avatar

Hey Jacob,

Is there any news on a timeframe when this issue is resolved?

Regards,
Bas

avatar

Hello @basdekort,

The fix has been implemented and is in the testing phase now. It will be available in the next release.
Best regards,

avatar

Hello, 

Thank you for being so patient! 

I'm pleased to inform you that a new version of Hub Business (2025.3.100) has been released, featuring the fix for your issue. 

Please let us know if this works or if you encounter any issues. 

Best regards, 

Maxim Robert

A fix for this issue has been implemented in version 2025.3.100