Does anyone know / Tested if it's possible to chain controls in a Designer page?

This message has been edited. Last edited by: Frans,

Ditto,

We will be getting into this very soon, seen demos as well.

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...

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

The following thread is related to this question. Please let me know if it doesn't answer your question.

http://forums.informationbuild...7041196/m/6297071196

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...

Thanks for all the input. This means also that the chaining will only work if you use the same master for all the containers on a page?

Would be nice to have an option to have a separate masterfile for the filters.

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?

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.

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,

Very interesting

Thanks dbeagan, that sheds some light on the possibilities we have.

That is a great technique! I love it when I learn something new!