Skip to main content
Question

Custom Fields Limit

  • September 29, 2025
  • 3 replies
  • 33 views

Forum|alt.badge.img+8

Hello everyone.

We have a potential use case for the assyst CMDB where the form could contain up to 150-200 custom fields. I’m wondering if anyone has any experience with this amount of custom fields in a custom form, and if so, whether there any impacts (such as performance)? 

Of course we have the possibility of splitting those fields in multiple item forms to reduce potential negative impacts, but any other comments or even suggestions are welcome.

Thanks!

3 replies

Link
Superhero (Customer)
Forum|alt.badge.img+23
  • Superhero (Customer)
  • 1265 replies
  • September 30, 2025

Hi ​@jdavidyoung07 

if you start a screen, IFS will load more data as usual.

Therefore, it should impact performance.

Keep the custom fields simple.

 


Forum|alt.badge.img+12
  • Hero (Customer)
  • 145 replies
  • October 6, 2025

You could also consider using configChars instead if there are common themes.


Forum|alt.badge.img+5
  • Do Gooder (Customer)
  • 12 replies
  • November 5, 2025

As a tip, we have found that older versions perform better than newer versions. You should therefore be cautious about updates and compatibility. The database structure of Assyst for objects is very complex, and a lot of data is always loaded along with the objects. This is probably also the reason why there are more and more restrictions for Objects in the new version.

 

My Tip: Keep it simple.