# 4.x ➡ 5.x

{% hint style="danger" %}
**Make sure that your Dashboard is running the Utility Core-Module version 2.1.0 or higher**
{% endhint %}

With **NRP 5.0.0**, we have changed how the sorting mechanism works in the Application, therefore we need to update some properties type in OC with the correct type in order to make the sorting works correctly. Do make sure your environments have ObjectUpdated properties for all object types. 

The OC changes will target 3 indexfields, and we are not going to add any new ones,\
indexfields to update:

* EventName
* PlanningHeadline
* AssignmentHeadline

These fields should have the type: `lowercase string`

```yaml
indexfields:
    - name: EventName
      type: STRING_LOWERCASE
      multivalued: false
      sortable: true
      readonly: false
      suggest: true
      description: Name of event
      
    - name: PlanningHeadline
      type: STRING_LOWERCASE
      multivalued: false
      sortable: true
      readonly: false
      suggest: true
      description: Planning headline
      
    - name: AssignmentHeadline
      type: STRING_LOWERCASE
      multivalued: false
      sortable: true
      readonly: false
      suggest: true
      description: Headline of assignment
```

{% hint style="success" %}
These OC changes has been applied to the standard-oc-config
{% endhint %}

{% hint style="warning" %}
A reindex is required after applying the changes for the indexfields for all types:

* Event
* PlanningItem
* Assignment
  {% endhint %}

In **NRP 5.0.0**, we cleaned up some configs that were hanging around in the settings, you need to remove these configs since these configs are now maintained in code, and no need to have them "configureable" anymore.\
Check out **Cleanup** page to see what configs you need to remove.

{% content-ref url="/pages/-MTB6zsDfZsBUsUJ49KO" %}
[Cleanup](/newsroom-planner/6.3.0/admin-guide/migration/4.x-5.x/cleanup.md)
{% endcontent-ref %}

When updating to **NRP 5.0.0**, you will get new sorting fields, since a new sorting functionality is shipped with **NRP 5.0.0**, you can check them out in Settings and modify them to fit your needs.

Go to **NRP** plugin settings and go to **Configurations** tab within the settings, and expand the **Sorting** section\
There you will find the new Sortings UI that you can change to fits your needs for each type:

* Event
* PlanningItem
* Assignment

![](/files/-MT0aoxlMg99-r5VJQ3L)

## Sorting keys

With the new sortings functionality as it is shown above, we add a custom set of sorting keys that you can sort your cards in the full application, the available keys are:

### **Event**

| **Sort name** | OC property    |
| ------------- | -------------- |
| Updated       | ObjectUpdated  |
| Start Date    | EventStartDate |
| Name          | EventName      |
| Prio          | EventUrgency   |

### **PlanningItem**

| **Sort name** | OC property       |
| ------------- | ----------------- |
| Updated       | ObjectUpdated     |
| Start Date    | PlanningStartDate |
| Name          | PlanningHeadline  |
| Status        | PlanningStatusHRM |
| Prio          | PlanningUrgency   |
| Sector        | PlanningSector    |

### **Assignment**

| **Sort name** | OC property             |
| ------------- | ----------------------- |
| Updated       | ObjectUpdated           |
| Start Date    | AssignmentStartDate     |
| Name          | AssignmentHeadline      |
| Status        | AssignmentStatusHRM     |
| Assignees     | AssignmentAssigneesName |

## Removed support for Drop down menus

As part of this version, to get filtering and sorting working properly, we removed the drop down menus (Prio, Sector etc), instead use the improved suggest search. 

## Changes to suggest search

We have implemented an experimental feature, where we let the user create personal favourites that then becomes buttons in the UI. In earlier versions, filters were shared between the different views in Newsroom Planner, in version 5 we have split this functionality to be per type instead. Old saved searches have been copied to all three views, and the user can then clean up searches per type if necessary. 


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.navigaglobal.com/newsroom-planner/6.3.0/admin-guide/migration/4.x-5.x.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.