Language messed up when exporting from Global Table to Excel

Question

question

tong asked Sep 27 2017 at 2:33 AM tannerp edited Jun 15 2018 at 2:57 PM

Language messed up when exporting from Global Table to Excel

I have a question about excel output. When I export from the Global Table of FlexSim17.1.2 to Excel, the language code is messy. Could you tell me how to solve this problem? Thank you!

Software Version:

FlexSim 17.1.2

Software Version:

Choose One

excel export messys code

messy-code.png (18.7 KiB)

· 4

Joerg Vogel commented · Sep 27 2017 at 5:59 AM

I can't reproduce the issue. I tested an export of a small table with german unique characters and different brackets all as strings. But perhaps you have to set the sheet file encoding to UTF-8. A workaround is to export a csv formated text file and import this file with the right encoding.

Maybe you can export the global table as a tree file from the model tree: right mouse button menu>Node > Save Node As... and append the file to your question. Then we are able to import your global table to an empty model and test, which settings are necessary to export the table.

2 ·

Phil BoBo ♦♦ commented · Sep 27 2017 at 1:40 PM

Please post an example model and the steps you are performing in order for us to replicate the issue you are seeing.

FlexSim has many ways to export data to Excel. We need more details in order to replicate the issue you are seeing.

2 ·

tong Phil BoBo ♦♦ commented · Oct 16 2017 at 6:30 AM

After opening the model,click the run button of script to achieve the export of global table.Then open demo1.xlsx in the modeldir(),you will find messys code.

0 ·

tong Phil BoBo ♦♦ commented · Oct 16 2017 at 6:31 AM

exceloutput.zip

0 ·

exceloutput.zip (26.2 KiB)

______

Cookie preferences

Your privacy is important to us and so is an optimal experience. To help us customize information and build applications, we collect data about your use of this site.

May we collect and use your data?

Learn more about the Third Party Services we use and our Privacy Statement.

Strictly necessary – required for our site to work and to provide services to you

These cookies allow us to record your preferences or login information, respond to your requests or fulfill items in your shopping cart.

YES

Improve your experience – allows us to show you what is relevant to you

These cookies enable us to provide enhanced functionality and personalization. They may be set by us or by third party providers whose services we use to deliver information and experiences tailored to you. If you do not allow these cookies, some or all of these services may not be available for you.

YES

NO

Customize your advertising – permits us to offer targeted advertising to you

These cookies collect data about you based on your activities and interests in order to show you relevant ads and to track effectiveness. By collecting this data, the ads you see will be more tailored to your interests. If you do not allow these cookies, you will experience less targeted advertising.

YES

NO

Are you sure you want a less customized experience?

We can access your data only if you select "yes" for the categories on the previous screen. This lets us tailor our marketing so that it's more relevant for you. You can change your settings at any time by visiting our privacy statement

Your experience. Your choice.

We care about your privacy. The data we collect helps us understand how you use our products, what information you might be interested in, and what we can improve to make your engagement with Autodesk more rewarding.

May we collect and use your data to tailor your experience?

Explore the benefits of a customized experience by managing your privacy settings for this site or visit our Privacy Statement to learn more about your options.

Answer 1 · 2017-10-16T15:52:47Z

Phil BoBo answered Oct 16 2017 at 3:52 PM tong commented Oct 17 2017 at 1:19 PM

Thanks for the example model. I'm able to replicate the issue you are describing using your sample model.

This appears to be a bug. I'll add a case to the dev list.

For now, you could follow Jörg's suggestion to use exporttable() to export each table to a csv file. Then use Excel's "From Text/CSV" Data import feature, which enables you to specify the text encoding, to load the csv files. When you select UTF-8, it loads this table correctly. See the image below:

exporttable-csv.png (196.3 KiB)

· 1

question