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. Moving forward, myibi is our community platform to learn, share, and collaborate. We have the same Focal Point forum categories in myibi, so you can continue to have all new conversations there. If you need access to myibi, contact us at myibi@ibi.com and provide your corporate email address, company, and name.
My experience has been if the master file has a hierarchy defined and those fields are used in where clauses they are automatically chained but the designer tool itself does not provide the ability to chain...
Thank you for using Focal Point!
Chuck Wolff - Focal Point Moderator WebFOCUS 7x and 8x, Windows, Linux All output Formats
Posts: 2128 | Location: Customer Support | Registered: April 12, 2005
And therein lies the rub for many of us. The new tools are really great, but they require a redesign of our metadata layers that can be overwhelming for legacy systems.
If you are starting with a clean slate it is much simpler than with MFDs designed only a few years ago. Joins in your focexecs are considered poor form, although for most of the last forty years that's how you did it.
I wish the metadata layer design transition had been stressed at Summit years ago when IBI started heading that way.
Rant over
WebFOCUS 8.2.03 - Production WebFOCUS 8.2.04 - Sand Box Windows 2012 R2 Server HTML, PDF, Excel In FOCUS since 1980
Posts: 115 | Location: Seattle, WA | Registered: April 07, 2015
So. is this saying that Chaining the controls in WebFOCUS Designer can only be done if the metadata has Hierarchy setup? I sure hope that is NOT what this is saying.
What about chaining data from 'flat' tables created from DataMigrator? What about chaining done in HTML Composer Controls... Chaining one dropdown list to another where they are populated from fexes... The way it's been done for years?
I'll be at every Designer session that Summit has to offer, maybe even attending the same one more than once... See you there...
In FOCUS Since 1983 ~ from FOCUS to WebFOCUS. Current: WebFOCUS Administrator at FIS Worldpay | 8204, 8206
Posts: 3132 | Location: Tennessee, Nashville area | Registered: February 23, 2005
So, What about chaining done in HTML Composer Controls... Chaining one dropdown list to another where they are populated from fexes... The way it's been done for years?
Posts: 3132 | Location: Tennessee, Nashville area | Registered: February 23, 2005
Summit will definately be the best place to get answers about how designer currently behaves and how it will be enhanced. You can create the chaining with composer and then use that html form in the designer for now.
Thank you for using Focal Point!
Chuck Wolff - Focal Point Moderator WebFOCUS 7x and 8x, Windows, Linux All output Formats
Posts: 2128 | Location: Customer Support | Registered: April 12, 2005
You can accomplish the chaining in Designer entirely within the fex:
-DEFAULT &aregion = '_FOC_NULL';
-DEFAULT &ast = '_FOC_NULL';
-DEFAULT &acity = '_FOC_NULL';
TABLE FILE ibisamp/ggsales
SUM UNITS
BY REGION
BY ST
BY CITY
BY DATE
ACROSS PCD
WHERE ( REGION EQ &aregion.(FIND REGION IN GGSALES|FORMAT=A11).Region.QUOTEDSTRING )
AND ( ST EQ &ast.(FIND ST IN GGSALES|FORMAT=A02,WITHIN=aregion).State code.QUOTEDSTRING )
AND ( CITY EQ &acity.(FIND CITY IN GGSALES|FORMAT=A20,WITHIN=ast).City.QUOTEDSTRING );
ON TABLE SET STYLE *
INCLUDE=IBFS:/FILE/IBI_HTML_DIR/ibi_themes/Warm.sty, $
ENDSTYLE
END
This message has been edited. Last edited by: dbeagan,
WebFOCUS 8.2.06
Posts: 210 | Location: Sterling Heights, Michigan | Registered: October 19, 2010