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.
I ran your code in my local 7.6.11 Dev.Studio environment and I am experiencing the same behaviour.
When analyzing the resulting Excel spreadsheet I noticed a "shift" in the formula used to calculate the subtotals.
In the first section of the report corresponding to FCODE = 'B', there are 5 summary lines for MANGROEP = '019' that go from row 7 to row 11 and therefore the subtotals on MANGROEP 019 should be calculated as:
F12 Cell:
=SUM(F7:F11)
G12 Cell:
=SUM(G7:G11)
The actual values Excel is receiving from WebFOCUS are =SUM(F8:F12) and =SUM(G8:G12) respectively.
The exact same situation occurs in all of the =SUM expressions on both FCODE and MANGROEP.
I don't have much experience with EXL2K FORMULA so it puzzles me why that is happening. I'll play around a bit to see what else I can find but just wanted to let you know that your case can indeed be replicated, at least in 7.6.11 and for what I can see from your signature, 7.6.10.
Tony, did you try that code in your local 7.6.11 environment or did you do it in 7.6.2 environment only? I am just trying do determine if this could be a "version thing" ... (you can tell I have no idea of what's going on )
The actual values Excel is receiving from WebFOCUS are =SUM(F8:F12) and =SUM(G8:G12) respectively.
At least we know why Excel is complaining about circular references as those values above are the ones it has in the F12 and G12 cells. Not that it solves anything ...
Interesting .... removing the SUBHEAD on FCODE makes the formula expressions work appropriately. That's partially good news I hope! I'll keep playing ...
thanks for the effort so far... yes it seems to occure in the latest release 7.6.10 and I have strumbled upon this problem just by coincidence... I played also a bit more and when I remove this block of code
Using your exact code, I am running this against a 7.6.2 server (as Neftali mentioned) but, in my output, the subtotal line to which Neftali refers is row 11 and not row 12. The formulae in each of F11 and G11 are respectively =SUM(F6:F10) and =SUM(G6:G10).
My local EDA server in DS 7.6.11 is not working currently (security problems on install )
T
In FOCUS since 1986
WebFOCUS Server 8.2.01M, thru 8.2.07 on Windows Svr 2008 R2
WebFOCUS App Studio 8.2.06 standalone on Windows 10
Posts: 5694 | Location: United Kingdom | Registered: April 08, 2004
I have made a work around in this special case where this border coding is skipped
That's a much better workaround than removing the SUBHEAD altogether as I had done during my tests. It just never occurred to me that the style sheet definitions would be messing around the Excel formula output in such a way ... well, I think I'll need to pay more attention to styling when facing some of those "unexplainables" in the future .
the subtotal line to which Neftali refers is row 11 and not row 12
I also get the results in row 11 when testing against WF 5.3.4. However the same code running in 7.6.11 makes result appear one row shifted down
Taking the "easy" road, I first attempted to remove the title on the ACROSS field and sure enough now I had 1 less row to worry about but the circular reference was still there.
My next step was to comment the SUBHEAD out and this time the formula worked but the subheading was missing of course.
Frank's further testing showed that hiding the BORDER on DATA made the problem disappear ... this reminded me of some old cases reporting an extra blank line below the HEADING that appears magically when using BORDER with no known way to make it go. Well, I just re-run the code in 7.6.11 as originally posted and sure enough the blank line was there which explains why all of the results appear one row down when compared to Tony's results but seems like the guys at IBI "forgot" to account for that one line when producing the formula results.
This does not occur in my "old" version of WF anyway as BORDERs were not supported for EXL2K format until 7.6.9. I am thinking that that's exactly the release where this formula issue was introduced but not "discovered" until now. Francis just proved that the code works as expected up to 7.6.8.
It would be interesting to test the code in 7.6.9 at least to prove the theory ... not that it fixes the problem but it may help to further document the case to IBI.
EXL2K BORDER were introduced in 7.6.9 and that seems to be the same release where the EXL2K FORMULA issue started to appear (circular reference due to shifted cells "thanks" to the magic blank line WebFOCUS gives us after a HEADING whenever BORDERs are in place).