Configure function field are custom fields?

[pampapathi1]

Hi All,

I have an inquiry regarding the creation of function fields in the report for retrieving the duration between follow-up and closure in the incident table.

Therefore, my question is whether the function fields created in the report using 'configure function field' are stored in the tables under a specific column. Please clarify if configure function fields are considered custom fields?

Are there any limitations on creating function fields in the report (for ex: can the incident table accommodate 20 fields, or will it allow more than that to create)?

Please suggest me.

Thanks,

Pampa

[Abbas_5 · Accepted solution]

Hello @pampapathi1,

Function fields created using "configure function field" in ServiceNow reports are not stored in the database tables as custom fields. Instead, they are dynamically calculated and displayed at runtime based on the defined operations and data from other fields. There's no limit to the number of function fields you can create in a report, but there might be limitations on the total number of fields (including custom and standard fields) that a table can support. 

Elaboration:

• Function Fields are not Stored:

  Function fields in ServiceNow reports are not persistent database columns. They are calculations performed on-the-fly, using the data available in the report's data source. 
• Custom Fields vs. Function Fields:

  Custom fields are database columns that are added to a table and store data. Function fields, on the other hand, are defined within the reporting framework and do not store data in the database. 
• No Direct Limit on Function Fields:

  There isn't a specific limit on how many function fields you can create in a report. The primary concern is the total number of fields (both standard and custom) that a table can accommodate, which can have practical limits depending on the system's capacity. 
• Table Field Limits:

  While there isn't a specific limit on function fields, tables do have limits on the total number of fields they can support. For example, one system mentioned a limit of 65,535 fields. 
• Example:

  If you're calculating the duration between follow-up and closure, you would configure a function field to perform the date difference calculation using the "open date" and "close date" fields. The result of this calculation is displayed in the report but not stored as a new column in the incident table. 

  If this is helpful, please hit the thumbs up button and accept the correct solution by referring to this solution in future it will be helpful to them.

  Thanks & Regards,

  Abbas Shaik

[Ankur Bawiskar · Accepted solution]

@pampapathi1 

those won't get counted as custom fields and won't impact any licensing.

If my response helped please mark it correct and close the thread so that it benefits future readers.

[Abbas_5 · Accepted solution]

Hello @pampapathi1,

Function fields created using "configure function field" in ServiceNow reports are not stored in the database tables as custom fields. Instead, they are dynamically calculated and displayed at runtime based on the defined operations and data from other fields. There's no limit to the number of function fields you can create in a report, but there might be limitations on the total number of fields (including custom and standard fields) that a table can support. 

Elaboration:

• Function Fields are not Stored:

  Function fields in ServiceNow reports are not persistent database columns. They are calculations performed on-the-fly, using the data available in the report's data source. 
• Custom Fields vs. Function Fields:

  Custom fields are database columns that are added to a table and store data. Function fields, on the other hand, are defined within the reporting framework and do not store data in the database. 
• No Direct Limit on Function Fields:

  There isn't a specific limit on how many function fields you can create in a report. The primary concern is the total number of fields (both standard and custom) that a table can accommodate, which can have practical limits depending on the system's capacity. 
• Table Field Limits:

  While there isn't a specific limit on function fields, tables do have limits on the total number of fields they can support. For example, one system mentioned a limit of 65,535 fields. 
• Example:

  If you're calculating the duration between follow-up and closure, you would configure a function field to perform the date difference calculation using the "open date" and "close date" fields. The result of this calculation is displayed in the report but not stored as a new column in the incident table. 

  If this is helpful, please hit the thumbs up button and accept the correct solution by referring to this solution in future it will be helpful to them.

  Thanks & Regards,

  Abbas Shaik

[pampapathi1]

@Abbas_5 

Thank you for checking !!

[Ankur Bawiskar]

@pampapathi1 

yes they do get created in sys_dictionary for that table

There could be some limitations on how many function fields you create, please check docs.

But remember since they do some calculation, if you include more it might impact report performance.

If my response helped please mark it correct and close the thread so that it benefits future readers.

[pampapathi1]

Thanks @Ankur Bawiskar ,

To keep it short, do you say these fields are custom fields ?

Because we have a limitation not to use custom fields.

Thank you