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 think why this is happening is because my FOR item on the hierarchy column is writing the line first and then joining to the incoming record from the HOLD file. Finding no record to join to, FOCUS writes the NULL element.
This is a bit off-putting, visually, and I would like the ability to remove lines where the data on the line = 0. Any ideas?
Here's what I tried so far: 1. In the .fex that creates the HOLD file, coded WHERE AMT <> 0 2. In the .fex that creates the HOLD file, coded WHERE TOTAL AMT <> 0 3. Created a SET NODATA = OFF element 4. Coded in FML report WHERE AMT <> 0 5. Coded in FML report WHERE TOTAL AMT <> 0This message has been edited. Last edited by: T.Peters,
WebFOCUS: 7702 O/S : Windows Data Migrator: 7702
Posts: 127 | Location: San Antonio | Registered: May 29, 2009
Ok, I figured out a solution and Tony, your suggestion helped foster the realization of what to do.
So I couldnt just put WHEN EXISTS on the line itself because when I did that I lost the parent record. But then I remembered that I can place a record on the report that shows JUST the header itself. So what I did was checked "USE MULTIPLE VALUES" box and changed my TAG line to "SHOW ONLY CHILDREN TO LEVEL". I added another tag line for the same FML element and on this line, I coded "SHOW SELECTED ITEM". On the TAG line where I displayed the children only, I put the WHEN EXISTS statement to eliminate the null records.
Heres an example of my code:
TABLE FILE FML_HIERARCHY_CON
SUM
'J0.SEG01.COMP_CURR_ACTUAL'
'J0.SEG01.COMP_CURR_BDGT'
'J0.SEG01.COMP_LAST_ACTUAL'
FOR
'FML_HIERARCHY_CON.FML_HIERARCHY_CON.LN_SEQ'
"REVENUE" LABEL R1 OVER
'3' AS 'MTG INSURANCE PRODUCTS' LABEL HDRMTGINS OVER
'3' GET CHILDREN 1 AS CAPTION LABEL MTGINSPRD WHEN EXISTS OVER
BAR AS '-' OVER
'3' ADD 1 AS 'TOTAL MORTGAGE INSURANCE PRODUCTS: ' LABEL TTLMTGINSPRD OVER
" " LABEL R6 OVER
'4' AS 'CREDIT UNION PRODUCTS' LABEL HDRCUPRD OVER
'4' GET CHILDREN 1 AS CAPTION LABEL CUPRD WHEN EXISTS OVER
BAR AS '-' OVER
'4' ADD 1 AS 'TOTAL CREDIT UNION PRODUCTS:' LABEL TTLCUPRD
Thanks for the help.
WebFOCUS: 7702 O/S : Windows Data Migrator: 7702
Posts: 127 | Location: San Antonio | Registered: May 29, 2009