VJ: Marked this version for translation

2026-03-13T12:54:47Z

Marked this version for translation

VJ: Created page with " {{News |Block code change functions |module=System |group=Base registers |version=546W2603 |revision=0 |case=CORE-7792 |published=2026-03-13 }} Block code chan..."

2026-03-13T12:54:37Z

Created page with "<translate> {{News |Block code change functions |module=System |group=Base registers |version=546W2603 |revision=0 |case=CORE-7792 |published=2026-03-13 }} Block code chan..."

New page
<translate>
{{News
|Block code change functions
|module=System
|group=Base registers
|version=546W2603
|revision=0
|case=CORE-7792
|published=2026-03-13
}}

Block code change functions

We have implemented an improvement in Marathon related to how codes are used in the system.

Codes are used in databases to create references between different tables.

For example, a project manager on a project is indicated by registering the employee code in the project manager field.

In many systems, internal codes that are not visible to the user are used. In Marathon, we have chosen to work with visible codes—partly to enable quick registration of references for those who know the code by heart, and partly to be able to display information in a more compact and clear format in tables with many columns.

Since codes are also used for references from our BI system, our new function Engage, and other external systems, it is important that they are stable and consistent.

To ensure that no references risk pointing incorrectly in the future, we will therefore remove the possibility to change existing codes in Marathon.

This change strengthens data quality and contributes to a more robust and reliable overall solution in a world with increasing interaction between different systems.

When the ability to control the codes decreases, a minor adjustment in the way of working may be needed.

At the same time, it opens up for a more user-friendly, modern, and consistent way of working in the system.

Instead of entering a code directly into a field, we recommend that you use the quick search function, which searches by names.

This makes the registration both smoother and more intuitive, especially when a code is not remembered.

Similarly, we recommend that you choose to display names instead of codes in tables wherever possible.

This provides a clearer and more readable overview.

Change code is blocked in the following registers:

Project|Backoffice|Base registers: Employees, Clients & Projects, Fee codes, Purchase codes and Other codes.

Media|Backoffice|Base registers: Clients, Agreements and Media.

Accounting|Backoffice|Base registers: Suppliers and Asset types.

</translate>

@@ Line 1: / Line 1: @@
 <translate>
 {{News
 |Block code change functions
@@ Line 10: / Line 11: @@
 }}
 <b>Block code change functions</b>
 We have implemented an improvement in Marathon related to how codes are used in the system.
 Codes are used in databases to create references between different tables.
 For example, a project manager on a project is indicated by registering the employee code in the project manager field.
 In many systems, internal codes that are not visible to the user are used. In Marathon, we have chosen to work with visible codes—partly to enable quick registration of references for those who know the code by heart, and partly to be able to display information in a more compact and clear format in tables with many columns.
 Since codes are also used for references from our <u>BI system</u>, our new function <u>Engage</u>, and <u>other external systems</u>, it is important that they are stable and consistent.
 To ensure that no references risk pointing incorrectly in the future, we will therefore remove the possibility to change existing codes in Marathon.
 This change strengthens data quality and contributes to a more robust and reliable overall solution in a world with increasing interaction between different systems.
 When the ability to control the codes decreases, a minor adjustment in the way of working may be needed.
 At the same time, it opens up for a more user-friendly, modern, and consistent way of working in the system.
 Instead of entering a code directly into a field, we recommend that you use the quick search function, which searches by names.
 This makes the registration both smoother and more intuitive, especially when a code is not remembered.
 Similarly, we recommend that you choose to display names instead of codes in tables wherever possible.
 This provides a <u>clearer and more readable overview</u>.
 Change code is blocked in the following registers:
 <b>Project|Backoffice|Base registers</b>: Employees, Clients & Projects, Fee codes, Purchase codes and Other codes.
 <b>Media|Backoffice|Base registers</b>: Clients, Agreements and Media.
 <b>Accounting|Backoffice|Base registers</b>: Suppliers and Asset types.

News:Block code change functions - Revision history

VJ: Marked this version for translation

VJ: Created page with " {{News |Block code change functions |module=System |group=Base registers |version=546W2603 |revision=0 |case=CORE-7792 |published=2026-03-13 }} Block code chan..."