Calculated Value Formula displaying uniqueName instead of caption

Answered
Rafael Felipe Cordeiro asked on January 12, 2026

Hi,

Could you please advise if it's possible to configure the Flexmonster formula area to display the field's caption instead of its uniqueName?

My issue is that after creating a calculated value and then renaming the source field's caption, the formula still references the original uniqueName. This behavior causes confusion, particularly in larger reports, making it difficult to understand which field is being used.

Any suggestions for a setting or workaround would be very helpful.



5 answers

Public
Maksym Diachenko Maksym Diachenko Flexmonster January 13, 2026

Hello, Rafael,

Thank you for contacting us.

To resolve this issue, we recommend using the useCaptionsInCalculatedValueEditor option. With this option enabled, the formula area will display captions instead of unique names. Please note that this option works not only for calculated values, but for all field captions.

We are looking forward to hearing your feedback.

Best regards,
Maksym

Public
Maksym Diachenko Maksym Diachenko Flexmonster January 28, 2026

Hello, Rafael,

Hope you are doing well.
We are wondering if you tried using the useCaptionsInCalculatedValueEditor option.
Looking forward to hearing your feedback.

Best regards,
Maskym

Public
Rafael Felipe Cordeiro January 29, 2026

Hello Maskym,

Thank you for reaching out about the useCaptionsInCalculatedValueEditor option.

Yes, I have been implementing this feature in our application. However, I have a few questions about the proper usage and structure.

1 - Where should this option be placed? I'm currently setting it in `report.options`, but should it also be set at the root level or in other specific locations?

2 - Could you provide the complete expected structure for this option? For example:

options: {

        useCaptionsInCalculatedValueEditor: true,

        formula: {

                useCaptionsInCalculatedValueEditor: true, // should it be here?

        }

}

  • 3 - Persistence: When using setOptions() and getOptions(), sometimes I notice that getOptions() returns null initially. What's the recommended approach to ensure the option persists correctly across report loads and user configurations?

 

  • 4 - Integration with saved configurations: How should this option behave when users have saved report configurations that don't include this setting? Should it always default to true?

Public
Maksym Diachenko Maksym Diachenko Flexmonster January 30, 2026

Hello, Rafael,

Thank you for your reply.

Placement of useCaptionsInCalculatedValueEditor
The useCaptionsInCalculatedValueEditor option should be set in the root level of the OptionsObject, as is shown in this example: https://jsfiddle.net/flexmonster/x2kovjbn/

Inconsistencies in the getOptions result
To ensure that the getOptions API call always returns correct results, we recommend using it after the reportcomplete event. This method returns null before the report is loaded, since this and many other API methods also depend on the report being fully initialized (see list of methods depending on reportcomplete). We have prepared an example of using the getOptions within the reportcomplete handler: https://jsfiddle.net/flexmonster/4caebxdr/

Apply useCaptionsInCalculatedValueEditor to previously saved reports
The useCaptionsInCalculatedValueEditor value is false by default. However, you can set it to true for older reports that do not have this option defined. To do this, you can specify the option within the global configurations. Configurations specified in the global object are applied to all reports, including those loaded from file or URL. Check this JSFiddle example with useCaptionsInCalculatedValueEditor defined in global config: https://jsfiddle.net/flexmonster/fx8q2zca/

Please let us know if our answer helped you.

Best regards,
Maksym

Public
Maksym Diachenko Maksym Diachenko Flexmonster 5 hours ago

Hello, Rafael,

Hope you are doing well.
Could you please let us know if these suggestions helped and whether the useCaptionsInCalculatedValueEditor option now works as expected on your side?
Please let us know if any further assistance is needed.

Best regards,
Maksym

Please sign in or register to submit your answer