Today, when autogenerating translation and exporting to Excel, only the manual entered instruction texts are included. I suggest to include both keystrokes and values in data-dependent steps in the export function.
Very often, we create recordings where the keystrokes differ from language to language. Let me give you an example. In Microsoft Business Central, you frequently search for a specific function/page. The name of the pages naturally differs in the various localizations. Below is an example.
- English: Wizard
- German: Assistent
- Danish: Guide
Having the keystrokes included in the Excel translation would greatly help us complete the replays in other languages.
Another critical issue when replaying in different languages is the data-dependent steps. Let me explain this with the following example.
I have a list with the following records (lines):
In the English recording, I selected the Purchase line, and when replaying in the English, everything runs beautifully smooth. However, when I do replay in the German Business Central, the line in Business Central is now called Einkauf. ClickLearn tries its best line but naturally fails (can't find the record Purchase).
Today, translating data-dependent steps is an extremely time-consuming manual task. Having the captured values from the data-dependent steps included in the translation export to Excel would be distinctly beneficial and considerably help us achieving great replays in other languages.