Focal Point Banner


As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.

Join the TIBCO Community
TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.

  • From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
  • Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
  • Request access to the private WebFOCUS User Group (login required) to network with fellow members.

Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.


Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     [SOLVED] US/Unit Seperator vs. Dash

Read-Only Read-Only Topic
Go
Search
Notify
Tools
[SOLVED] US/Unit Seperator vs. Dash
 Login/Join
 
Platinum Member
posted
I have a *.fex that displays fine in HTML.

However - when export to Excel - it blows up with the the following message

Removed Part: /xl/sharedStrings.xml part with XML error. (Strings) Illegal xml character. Line 75, column 26.
Removed Records: Cell information from /xl/worksheets/sheet1.xml part

I was able to track this down to a specific row - and specific field in the report....the address.

Community Center, 1425 – 4th ST NE, Somewhere, MN, 55123

Converting to Hex - I can clearly see the issue is the "dash".

The dash is secretly a hex value of 1f

When I manually remove the dash - or convert said dash to a 2d hex value - it works fine.

What's the best way to address this? I'm pulling from a Unicode SQL server table. I'd prefer, if possible, to avoid doing a string replace/CTRAN - because I think if the 1f/Unit Separator field is giving me grief now - I'm guessing there's some other data that will too.

Same goes for the report - if I can turn it on in this report - I'm sure it'll blow up in some other report that pulls in the address field.

Is there some other server setting that allows the 1f field to export to XLSX?

I read about the NLS - but I'm not sure if that's the right solution. Could be - but I'm more of a code geek than a configuration geek - so I may be interpreting that incorrectly. Our CODE_PAGE is set to 437 - U.S. English and the LANG is set to AMENGLISH.

Any suggestions?

This message has been edited. Last edited by: <Kathryn Henning>,


webFOCUS 8207.15
WindowsServer 2019
 
Posts: 120 | Location: Minnesota | Registered: August 26, 2013Report This Post
Master
posted Hide Post
Did you try with HTMLFORMTYPE=XLS?
 
Posts: 542 | Location: Dearborn, MI | Registered: June 03, 2009Report This Post
Platinum Member
posted Hide Post
I was able to have the source system change the dash to fix my problem....so I fixed this in the data - rather then with webFOCUS.


webFOCUS 8207.15
WindowsServer 2019
 
Posts: 120 | Location: Minnesota | Registered: August 26, 2013Report This Post
  Powered by Social Strata  

Read-Only Read-Only Topic

Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     [SOLVED] US/Unit Seperator vs. Dash

Copyright © 1996-2020 Information Builders