none
Special Characters RRS feed

  • Question

  • Hello, does someone knows how to make that "power bi" display accents, ñ or special characters like º ª, thanks.
    Regional configuration: Spain, international alphabet.
    Data source: json file.
    Tuesday, January 29, 2019 11:46 AM

Answers

  • Hi Sergio

    I was able to reproduce your issue.

    My guess is that your json file (it's a text file) is not encoded in UTF-8 but using a different encoding.

    To reproduce your problem, using Windows’ Notepad I copied your sample and save it with a “.json” extension in ANSII encoding. If I use UTF-8 encoding instead, there’s no problem at all with the Power Query import.

    You can try saving a copy of your json file with a different encoding (UTF-8) and importing this copy, or, at the first step of the Power Query editor, forcing the encoding to a different value. See the next screenshot.


    Tell us if this solved your problem.

    Saludos,

    Daniel

    Monday, February 4, 2019 6:36 PM

All replies

  • Hi Sergio. Where are you seeing the special characters displayed incorrectly? In the Power Query Editor?

    Ehren

    Thursday, January 31, 2019 12:28 AM
    Owner
  • It happens to me both in the visualization and in the Power Query Editor.

    The operating system and the application are configured as Spanish, international alphabet.

    In the json file the data looks good with the Visual Studio.

    I'm logged in but will not let me insert images,sry.

    Thanks for the help Ehren.

    Thursday, January 31, 2019 11:13 AM
  • I just tried creating a json file by pasting in the characters you listed above. Everything seems to be fine in the Power Query Editor.

    Can you share a sample file (with any sensitive info removed) that demonstrates the issue?

    Thanks,
    Ehren

    Thursday, January 31, 2019 6:49 PM
    Owner
  • Sorry for the delay, I had a few days off.

    When I try to send you an image I get this notice:

    "Body text cannot contain images or links until we are able to verify your account."

    I'm logged in so I do not know how I can send you images.

    This is a short example:

    {
      "listaPedidos": {
        "fecha_inicio": "01/12/2018 0:00:00",
        "fecha_fin": "31/12/2018 0:00:00",
        "cod_empresa": "19",
        "pedidos": [
          {
            "cod_pedido": 65597,
            "fecha_pedido": "01-12-2018",
            "cod_seccion": 1,
            "cantidad_carga": 0,
            "cod_operacion": 1,
            "nombre_barco": "ENDEAVOR",
            "nombre_lugar": "A2",
            "nombre_mercancia": "Contenedor",
            "cod_jornada": "1",
            "cod_tipo_servicio": 0,
            "trafico_internacional": 1,
            "especialidadesSolicitadas": [
              {
                "cod_especialidad": 1,
                "descripcion_especialidad": "Capataz",
                "cod_grupo_profesional": 1,
                "descripcion_grupo_profesional": "CAPATAZ",
                "cantidad": 1,
                "trabajadores": [
                  {
                    "num_trabajador": 5530,
                    "nombre_trabajador": "RAUL ABAD MARTINEZ",
                    "ett": 0,
                    "remates": 0
                  }
                ]
              },
              {
                "cod_especialidad": 2,
                "descripcion_especialidad": "Contenedor (Buque)",
                "cod_grupo_profesional": 2,
                "descripcion_grupo_profesional": "C.MERCANCIA",
                "cantidad": 2,
                "trabajadores": [
                  {
                    "num_trabajador": 5563,
                    "nombre_trabajador": "JULEN GARCIA MEZQUITA",
                    "ett": 0,
                    "remates": 0
                  },
                  {
                    "num_trabajador": 5825,
                    "nombre_trabajador": "DANIEL MIGUEL VELADO",
                    "ett": 0,
                    "remates": 0
                  }
                ]
              },
              {
                "cod_especialidad": 3,
                "descripcion_especialidad": "Contenedor (Almac)",
                "cod_grupo_profesional": 2,
                "descripcion_grupo_profesional": "C.MERCANCIA",
                "cantidad": 1,
                "trabajadores": [
                  {
                    "num_trabajador": 5592,
                    "nombre_trabajador": "CARLOS HERRERO HERNANDEZ",
                    "ett": 0,
                    "remates": 0
                  }
                ]
              },
              {
                "cod_especialidad": 13,
                "descripcion_especialidad": "Grúa Transtainer",
                "cod_grupo_profesional": 4,
                "descripcion_grupo_profesional": "CONDUCTOR",
                "cantidad": 1,
                "trabajadores": [
                  {
                    "num_trabajador": 5873,
                    "nombre_trabajador": "ALAIN MEZO BAZAL",
                    "ett": 0,
                    "remates": 0
                  }
                ]
              },
              {
                "cod_especialidad": 14,
                "descripcion_especialidad": "Grúa Portainer",
                "cod_grupo_profesional": 4,
                "descripcion_grupo_profesional": "CONDUCTOR",
                "cantidad": 4,
                "trabajadores": [
                  {
                    "num_trabajador": 5523,
                    "nombre_trabajador": "JOSE LUIS BARBA CORTES",
                    "ett": 0,
                    "remates": 0
                  },
                  {
                    "num_trabajador": 5538,
                    "nombre_trabajador": "TOMAS HERNANDO ORTUZAR",
                    "ett": 0,
                    "remates": 0
                  },
                  {
                    "num_trabajador": 5558,
                    "nombre_trabajador": "ALBERTO CASQUERO PRESA",
                    "ett": 0,
                    "remates": 0
                  },
                  {
                    "num_trabajador": 5606,
                    "nombre_trabajador": "ASIER URANGA ORTIZ",
                    "ett": 0,
                    "remates": 0
                  }
                ]}
            ]
          }
        ]
      }
    }

    Thanks for your help


    shows "almac�n" instead of "almacén"
    shows "JOSE M�" instead of "JOSE Mª"
    shows "I�AKI" instead of "IÑAKI"
    Operating system and power bi configured as Spanish (international alphabet).With Visual Studio the json file looks perfectly.
    Monday, February 4, 2019 11:07 AM
  • Hi Sergio

    I was able to reproduce your issue.

    My guess is that your json file (it's a text file) is not encoded in UTF-8 but using a different encoding.

    To reproduce your problem, using Windows’ Notepad I copied your sample and save it with a “.json” extension in ANSII encoding. If I use UTF-8 encoding instead, there’s no problem at all with the Power Query import.

    You can try saving a copy of your json file with a different encoding (UTF-8) and importing this copy, or, at the first step of the Power Query editor, forcing the encoding to a different value. See the next screenshot.


    Tell us if this solved your problem.

    Saludos,

    Daniel

    Monday, February 4, 2019 6:36 PM
  • Hi Daniel, thanks for your help.

    From power bi changing the encoding of the json file to utf-8 (like in the image) i still get the same problem, but if i open it as text and change the encoding, importing it from power bi looks good.

    The archives json are generated in a web application as queries defined by the user, so i will have to change the encoding before they reach power bi. Thank you very much and I give your answer as a solution.

    edited:

    Hello Daniel again, commenting that importing from power bi the json file with 1252 encoding, as you indicate (instead of utf-8), the data looks correct.

    So I have two solutions to my problem:

    1-that the files come encoded as utf-8

    2-change the configuration when importing them to 1252 (Western European)

    Thank you very much again.


    Tuesday, February 5, 2019 7:36 AM