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.
We recently upgraded to webfocus 8 and wanted to get all of our existing excel reports into xlsx. When converting output type to XLSX we found that any images we embedded into our excel reports no longer function, but rather the file appears to be corrupted and gives "Removed Part: /xl/sharedStrings.xml part with XML error. (Strings) The name in the end tag of the element must match the element type in the start tag. Line 8, column 45" Any insight would be appreciated.This message has been edited. Last edited by: <Kathryn Henning>,
There are a few things which we're aware of that may cause this error. I'd like to get a little more information from you to see if we can narrow this down.
What version of Excel are you using?
Does any one cell have more than 536 characters in it?
Could you please post the code that is creating the XLSX file to this topic? Please ensure to surround the code with code tags (the last button on the tool bar).
ENGINE SQLSYB SET DEFAULT_CONNECTION SYBASE
SQL SQLSYB
EX operations..TrailerIdleTimeSummaryWF 13;
TABLE FILE SQLOUT
PRINT *
ON TABLE HOLD AS IDLESUM
END
DEFINE FILE IDLESUM
REGIONS/A3000='[IMG]\\HAVOK\sybase\REGIONS.GIF[/IMG] ';
REGIONSLINE/A3000='[IMG]\\HAVOK\sybase\REGIONSLINE.GIF[/IMG] ';
CBReg/A3000='[IMG]\\HAVOK\sybase\CB.GIF[/IMG] ';
CBLines/A3000='[IMG]\\HAVOK\sybase\CBLINES.GIF[/IMG] ';
END
TABLE FILE IDLESUM
SUM
MAX.IDLESUM.IDLESUM.region NOPRINT AS 'MAX,IDLESUM.IDLESUM.region'
REGIONS AS ''
REGIONSLINE AS ''
HEADING
"All Regions"
ON TABLE SET PAGE-NUM OFF
ON TABLE NOTOTAL
ON TABLE PCHOLD FORMAT XLSX OPEN
ON TABLE SET STYLE *
TITLETEXT='Regions',
$
TYPE=REPORT,
COLUMN=N3,
WRAP=8.000000,
$
TYPE=REPORT,
COLUMN=N2,
WRAP=8.000000,
$
ENDSTYLE
END
-RUN
TABLE FILE IDLESUM
SUM
MAX.IDLESUM.IDLESUM.region NOPRINT AS 'MAX,IDLESUM.IDLESUM.region'
CBReg AS ''
CBLines AS ''
HEADING
"CB Region"
ON TABLE SET PAGE-NUM OFF
ON TABLE NOTOTAL
ON TABLE PCHOLD FORMAT XLSX CLOSE
ON TABLE SET STYLE *
TITLETEXT='CB',
$
TYPE=REPORT,
COLUMN=N3,
WRAP=8.000000,
$
TYPE=REPORT,
COLUMN=N2,
WRAP=8.000000,
$
ENDSTYLE
END
Thank you for the information and for posting your code. There are several known issues that produce the error message that you provided in your first post. One of them involves the use of AS names which your code includes, but the specifics are different.
We can take a more detailed look at this. Please open a case on InfoResponse Online.