Introduction
Advanced Insights now lets you use up to 15 user additional fields and up to 15 course additional fields in each dashboard, instead of five of each. To support this, Docebo replaced the legacy additional field parameters with two new parameters and a new way of reading additional fields. This article explains what Docebo migrates for you, what you need to migrate yourself and how to do it before the legacy fields are removed on February 26, 2027.
Who needs to act
| Your situation | What you need to do |
|---|---|
| Your dashboards do not use additional fields. | Nothing. You can use up to 15 additional fields whenever you need them. |
| Your dashboards use additional fields in visuals, tables, charts, filters, conditional formatting or calculated fields. | Replace the legacy fields with new calculated fields, as described in this article. |
What changed
Previously, each additional field had its own dedicated parameter, which limited you to five fields for users and five for courses. Each dashboard used eleven single-value parameters.
| Parameter | Number |
|---|---|
| Language of the additional fields | 1 |
CustomUserAdditionalField1 to CustomUserAdditionalField5
|
5 |
CustomCourseAdditionalField1 to CustomCourseAdditionalField5
|
5 |
Now, two multi-value parameters support up to 15 additional fields each: CustomUserAdditionalFields and CustomCourseAdditionalFields. Advanced Insights gives you the fields through the consolidated dataset fields user_additional_fields and course_additional_fields, and you read each additional field with a calculated field. The language parameter no longer exists. Docebo reads the labels in the default language of your platform, in the same way it does for branches.
Please note: We recommend using up to 15 user additional fields and up to 15 course additional fields in a dashboard. Using more additional fields can increase the loading time of the dashboard.
What Docebo migrates automatically
Docebo converts the parameters for you. The values that you entered in the Static default value field of your legacy parameters move, in the same order, to the new CustomUserAdditionalFields and CustomCourseAdditionalFields parameters. The language selector for additional fields no longer appears, and the default language of your platform applies automatically.
What you migrate yourself
Docebo cannot detect every place where a dashboard uses an additional field, so you need to replace the legacy fields yourself. Duplicate the dashboard before you make any changes.
Please note: Keep the existing selections of the legacy parameters and their order unchanged until you have migrated the whole dashboard. Changing or reordering them changes the values that the legacy fields return and can affect visuals that you have not migrated yet.
First, list every place where the dashboard uses an additional field. Check visuals, dashboard-level and visual-level filters, conditional formatting rules and your own calculated fields, which often start with an equals sign. Filters and conditional formatting are easy to miss because they are not visible on the surface of the dashboard. Write the list down before you start, with one row for each field, dashboard and location.
Next, create a calculated field for each additional field that you use, as described in the section Creating a calculated field for an additional field of the article Using Advanced Insights. If you previously used the translation field to get the label of the additional field, use the .label property.
Then, for each place on your list, open the visual, the filter or the conditional formatting rule, remove the legacy field and add the new calculated field in its place. Apply again any formatting, sorting or alias that was attached to the legacy field, and save.
Finally, check the dashboard. Confirm that the values match the values that the dashboard showed before, test each filter that uses an additional field, trigger each conditional formatting rule and check that no visual shows a blank or null column. Tick each field off your list as you go.
Quick reference
| Item | Detail |
| Maximum additional fields | 15 for users and 15 for courses, up from 5 |
| New parameters |
CustomUserAdditionalFields and CustomCourseAdditionalFields
|
| Index rule | Position in the list minus 1, so the valid range is 0 to 14 |
| Language | Platform default, applied automatically, with no selector |
| Places to check | Visuals, filters, conditional formatting and calculated fields |
| Removal date of the legacy fields | February 26, 2027 |
Common mistakes
Tip: Avoid these common mistakes. Using the position of the additional field instead of the index (the second field has index 1, not 2). Using .value when you need .label. Replacing visuals but forgetting filters and conditional formatting. Assuming that automatic means complete, because parameters migrate automatically but the usages inside dashboards do not. Changing the order of the list, because every index after the change shifts.