An issue with parsing .json file that consists of a list of .jsons

Question

Hi everyone, 
 
 recently I encountered an issue with parsing a .json file. 
 Here is how the file looks: 
 
 This is a list of jsons within a json. Values for the following keys need to be localized: LanguageID, RibbonText, Notification, Buttons (if the strings is not "null"), Description, Subject and Value. 
 Until now I have been using out of the box .json parser (Add-in JSON Parser). However, when the file was updated and a new .json (with the exact same structure) has been added to the file between already existing .jsons and, as a result I had a leverage loss. 
 Below is a screenshot for visualization: 
 
 Since the structure for all of the .jsons within this file is the same and there are no unique keys, new json jumped in the place of the one with name "AutoRunFailed". For Passolo, string IDs remained the same, but the source changed. I lost leverage for everything that is below the red arrow (highlighted in yellow). Strings had the untranslated status and Passolo suggested teh old translations. 
 I was able to recover my translations, by moving the new .json to the very end of the file and leveraging translation from a copy of Passolo project, however this is not a long term solution. The same issue will come up again when this file is updated. 
 I contacted the support and they confirmed that there is no other way around. So we tried to come up with a custom txt parser. Using value for "Name" as string ID (in yellow) for all of the values in green - screenshot below. 
 
 I managed to achieve that very easily with the first string (String id: "AutoRunValidationError" Parsed string: "1033"). Simply by doing the following:

However I am stuck when I want to move on to the next strings. 
 With help from support I managed to set " AutoRun ValidationError " as string id for "RibbonText" by doing the following: 
 
 I tried to use the same rule and changing "RibbonText" with "Notification" and it simply does not work. Ans support is not able to help here. 
 
 Does anyone has an idea how to make it work so that I can AutoRun ValidationError set as string id for all the values that need to be localized? 
 
 Or maybe we can achieve that with a different parser? 
 
 I would very much appreciate your help with this ;) 
 
 I am using Passolo 2022

Achim Herrmann · Accepted Answer

Foremost, the statement from the support colleagues is correct that an unstructured JSON list is supported, but that it is then no longer possible to identify where a new list entry was inserted during the update. A solution approach using the text parser is promising, but I would proceed differently. Unfortunately, the file wasn't attached, and I didn't want to type it all out. So I only generated a small sample file and some adjustments are still necessary. 
 Define a Resource group that takes the content of "Name" as the group name: 
 
 Then define the translatable elements by naming them in a RegEx list (separated with | ), and use their strings as IDs within the groupings: 
 
 Please note that my list is just an example, you need to insert all your items you want to see in the translation list. This will then result in a nicely structured translation list that will also works when updates are inserting new JSON list items with a new "Name" content. 
 
 It might be necessary to add mappings when text strings do contain escaped double quotes and you might want to optimize the list view by activating the Inline Patterns for HTML, so that tags appear tagged in the translation editor.

Passolo > 1. General

An issue with parsing .json file that consists of a list of .jsons

Top Replies