thumb_up
thumb_down
link
Copy link
Copied
insert_emoticon
lmatfy
Copied

Translate the description of an article and wage component

In Profityou can translate descriptions of items (articles, etc.), routes, units and locations, etc. into multiple languages. The language setting in the properties of the sales contact or purchase contact ensures that the item is displayed and printed in the correct language.

Description

Example: 

Suppose you export your articles to sales contacts in Germany and England. You can have all the article descriptions translated into the sales contact’s language and print them on your quotations, orders, packing slips, etc.

By translating all your items and related texts into the sales/purchase contact’s language, you can display the translated descriptions in the entry layout and print them in a report. This function is particularly useful if you have to deal with multiple languages. Now you can use one field to display multiple languages in one and the same entry layout or print them in one report.

You can translate both tables with fixed codes and master data created by you (items, units, article groups, etc). Which fields can and cannot be translated, depends on the table. It is often the code, the description, the extra description and the remark (in the footer of the entry layout).

You can also use this function to translate wage components and/or job titles. If so, specify the deviating language in the employee’s properties.

If you add an order, you can no longer change the translated descriptions, etc., in the entry layout. However, if you want to make changes, it is better not to translate, but to add a custom field and change this when entering data.

Translations can be imported.

If you want to translate (article) descriptions, first check if the language table contains the language that you want to translate into. Next you translate the descriptions of the articles, insofar as you think it is necessary. Add the fields that you have translated for each article to the order entry layout. Go to the sales contacts to set the language they are using. Finally you add orders for the sales contacts with different language settings. You then see the descriptions and the like in the language of the sales contact.

Procedure

  • Add a language code

    You can add a language code yourself.

  • Translate product descriptions

    In Profityou can translate descriptions of items (articles, etc.), routes, units and locations, etc. into multiple languages. The language setting in the properties of the sales contact or purchase contact ensures that the item is displayed and printed in the correct language.

  • Add a wage component translation

    In Profit you can translate descriptions of wage components into multiple languages. In this case, the language setting in the properties of the employee or employer ensures that the correct language appears on the pay slip.

  • Include fields in entry layouts

    You include the Translated item code, Translated item description, Translated additional item description and Translated item comment fields in the relevant entry layouts. When making an entry, you will then see the fields in your language and the language for the sales/purchase contact.

  • Use translated fields in a report

    You can print the translated fields in a report by adding specific fields to the report. The language in which the fields are printed depends on the language code in the properties of the debtor.

  • Set the language in the sales and/or purchase contact properties

    In the creditor and debtor properties, you can record which language they use. Based on this setting, fields in reports can be completed in that language instead of Dutch.

  • Import translations

    You can import the translations for each language. This applies to all translatable code tables, including wage components.

  • Update the database basic language

    In Dutch, Profit is released in new Versions, Builds and Updates. If you are using a basic language other than Dutch, it may occur that not everything in all environments is shown in your basic language. In this case, you can update the basic language.

Also see

Process

Language

Work area

bas