Hi @bernarddinon,

Sorry to hear that you've run into this issue. There's been some work done on the Excel format recently that has fixed a similar issue on reading non-UTF8 system encodings. It looks like it's just a build or so away from being released into FME 2019.2 and 2020. You'll want to look for build 19818 or higher for FME 2019.2, or build 20165 and higher for FME 2020.

 

 

I'll keep an eye on that and let you know when it's available to download. You can also subscribe to our downloads page to get notified when the new downloads are available. Hopefully that solves the issue for you, but if it doesn't, definitely let us know.

---

@jovitaatsafe

 

 

Thank for your answer. But we had installed FME Server 2019.1 in november 2019. Unfortunately we are not planning to update for the moment because we must also update FME server by an external person and must check all the workspace in FME_Server. For the moment, we Don't have time.

 

This problem of special charachter is not only with Excel. If i use a workspace Runner with this parameter, FME_DESKTOP stop the run besause i can read the value "â".

 

This problem was not present in FME 2018.

 

 

Is there a workaround for this encoding?

 

 

From FME 2016 to 2019.0 we have not big issues wiht update, but we find that FME 2019.1 contains a lot of new issues

 

 

Best Regards

 

 

 

---

@jovitaatsafe

 

 

Thank for your answer. But we had installed FME Server 2019.1 in november 2019. Unfortunately we are not planning to update for the moment because we must also update FME server by an external person and must check all the workspace in FME_Server. For the moment, we Don't have time.

 

This problem of special charachter is not only with Excel. If i use a workspace Runner with this parameter, FME_DESKTOP stop the run besause i can read the value "â".

 

This problem was not present in FME 2018.

 

 

Is there a workaround for this encoding?

 

 

From FME 2016 to 2019.0 we have not big issues wiht update, but we find that FME 2019.1 contains a lot of new issues

 

 

Best Regards

 

 

 

Unfortunately if it's an encoding issue, I don't think there is a workaround for it. One possibility in my mind is that since you can have multiple versions of FME installed at the same time (as long as they're installed in unique folders), you could give 2019.2 a try when the fix is released to be sure that the fix really applies to your issue. I'm not sure if development would be able to but I can definitely ask to see if the fix can be added into 2019.1.

We have a longer term project that we're working on to better handle encoding for attribute and feature type name support. But because it involves a lot infrastructure work, I understand it's a more involved process that will take more time. Sorry for the inconvenience!

---

@jovitaatsafe

 

 

Thank for your answer. But we had installed FME Server 2019.1 in november 2019. Unfortunately we are not planning to update for the moment because we must also update FME server by an external person and must check all the workspace in FME_Server. For the moment, we Don't have time.

 

This problem of special charachter is not only with Excel. If i use a workspace Runner with this parameter, FME_DESKTOP stop the run besause i can read the value "â".

 

This problem was not present in FME 2018.

 

 

Is there a workaround for this encoding?

 

 

From FME 2016 to 2019.0 we have not big issues wiht update, but we find that FME 2019.1 contains a lot of new issues

 

 

Best Regards

 

 

 

Hello, thanks for your answer.

 

We will appreciate if the fix can be added into 2019.1 because it's a critical problem with writer and workspace Runner for our business

 

When you said we can have multiple versions of FME installed in unique folder. It's only for desktop or also for FME Server?

 

 

Best regards

---

Hello, thanks for your answer.

 

We will appreciate if the fix can be added into 2019.1 because it's a critical problem with writer and workspace Runner for our business

 

When you said we can have multiple versions of FME installed in unique folder. It's only for desktop or also for FME Server?

 

 

Best regards

@bernarddinon, you can install multiple version of FME Desktop, but not multiple versions of FME Server.

If possible, can you let me know when you have tried FME Desktop 2019.2 build 19818 (not available yet at the time of writing this) and if it works for you? We want to be certain that this is the correct fix for your issue in order for our development team to consider backporting a fix, which I understand is a high risk thing for them to do. Thanks!

---

@bernarddinon, you can install multiple version of FME Desktop, but not multiple versions of FME Server.

If possible, can you let me know when you have tried FME Desktop 2019.2 build 19818 (not available yet at the time of writing this) and if it works for you? We want to be certain that this is the correct fix for your issue in order for our development team to consider backporting a fix, which I understand is a high risk thing for them to do. Thanks!

@jovitaatsafe : Thank you for your answer.

 

 

I will test the 2019.2 build 19818 when it's available. I will see with my IT service to instal it.

 

 

I will suscribe to your download page to get the information.

 

 

 

Best regards

 

 

---