Current filter:
                                You should refresh the page.
                                  • Hello

                                    I'm trying to add a new JSON data source at run time in the end-user report designer.

                                    And the two issues i get are as follow:

                                    1. Special charracters as € are not displayed.
                                    2. I'm getting the message bad string when i try to add a new JSON data source. When i make the specifiek string shorter, the message disapears and i am able to use the JSON data source. Is there a max length of the strings when they are importerted? If yes, can i use longer strings?

                                    Regards,

                                    Kenneth

                                • Vasily (DevExpress Support) 07.17.2019

                                  Hi Kenneth,

                                  Thank you for contacting us. It is difficult to tell your how to resolve these issues without replicating them on our side. So, please share the code that you are using to create a JsonDataSource component at runtime (in case you do this in code). Also send us the JSON data that you are trying to load to your JsonDataSource. This way we will be able to replicate and research both issues on our side.

                                • Customer83525 07.21.2019

                                  Hello Vasily,

                                  The problem with the json string is solved, there was indeed a probleem with the string in the json that didn't see on the first time.

                                  But is it posible to display special characters like €?

                                  Regards,

                                  Kenneth

                                1 Solution

                                Creation Date Importance Sort by

                                Fixed:


                                Additional information:

                                Hi Kenneth,
                                 
                                Thank you for your update. We replicated and fixed this issue.
                                 
                                With the fix, UTF-8 encoded JSON files should be loaded to reports and special characters will not be lost.