TreeTable Component - attributes for $selected[*]

I am trying to pass some query parameters to a new menu item added to the TreeTable component that drives the main menu in IDM 8. Documentation in the treetablelibrary.xml says:
<Comments> Define an action by supplying:
              - a name (action)
              - a label to display for the action, usually a message key (label)
              - the selections required for this action (selectionMode):
                "none", "oneOrNone" (optionally one selection), "single"
                (exactly one selection), "multi" (one or more), and "any"
                (any number of selections, including none).
              - the types of object this action applies to (selectionTypes)
              - the URL to route the action to (targetURL)
              - a map of parameters to pass to the targetURL (targetParameters)
                You can set session attributes by prefixing the parameter name
                with "Session:". You can reference the selected items by using
                a parameter value of "$selected[name]".
              - the type of this object for authorization purposes (authType).
                If omitted, selection type will be used.
              - the right required on the object to perform this action (requiredRight)
              - an ACL for the action (actionACL). If supplied, this overrides
                authType and requiredRight.
          </Comments>The question I have is: What are the attributes that are available for use with the $selected[*] syntax? I see 'id' and 'name' as examples (selected[id] and selected[name]), but would like to understand what else can be accessed in this way.
To clarify, here is the type of code I would be writing:
<argument name='targetParameters'>
                            <Map>
                                <MapEntry key='id' value='$selected[id]'/>
                                <MapEntry key='name' value='$selected[name]'/>
                            </Map>
                        </argument>Thanks for the help!

See if example 61 on the ADF Code corner helps:
http://www.oracle.com/technetwork/developer-tools/adf/learnmore/61search-in-rendered-trees-177577.pdf
http://www.oracle.com/technetwork/developer-tools/adf/learnmore/index-101235.html#CodeCornerSamples

Similar Messages

Setting screen attributes for select-option in subscreen

Hello SDN Community, I have researched this extensively in forums and found much helpful information in getting the select-option working in a subscreen. Also found information that discussed using standard AT SELECTION-SCREEN statements to process the sub-screen with.
I encountered problems when that from the LOOP AT SCREEN within the AT SELECTION-SCREEN OUTPUT, I set the INPUT/OUPUT attributes to zero, the field was still open for input when it displayed. For when I do this on other fields of my screen, they are "greyed out".
Has anyone any experience setting field attributes from within loop at screen for embedded select-option subscreen? Would appreciate any insight you might have.
Thank you,
Dean Atteberry.
P.S.- I put this thru the debugger and I can see the INPUT and OUTPUT attributes getting changed. But when displays, it is like the change didn't happen.
Full description of my processing below...
I have a screen with four radio-buttons. Under the first radio-button is my embedded subscreen with one SELECT-OPTION for AUFNR. Under the other three radio-buttons are single fields declared regular way in main screen.
In my PBO of main screen I have loop at screen that enables/disables INPUT and OUPTUT attributes based on which radio-button is selected. This prevents confusion from user entering values in fields other than the one the radio-button is selected for.
For my embedded select-option subscreen, I have an AT SELECTION-SCREEN OUTPUT statement in which I have a LOOP AT SCREEN. Within that, based on radio-buttons, I either enable or disable the INPUT and OUTPUT attributes for the S_AUFNR-LOW and S_AUFNR-HIGH fields.
Edited by: Dean Atteberry on Mar 25, 2009 4:39 PM

>> I think that you are trying to change select options within main screen, whereby it should be
>> changed in PBO of that subscreen. You said you do it in AT SELECTION-SCRREN OUTPUT which
>> will be only applicable for selection screen (I guess your main screen here). Do loop at screen in
>> PBO module of this subscreen not in PBO of the selection screen and see if that helps.
Hi Marcin, thank you for your reply. My "main screen" is not my "selection screen". Please allow me to further clarify...
My "main screen" has four radio buttons with a subscreen area under the first one and single fields under the others.
My "subscreen" is auto-generated by Selection-Screen and Select-Options statements which are in my TOP module.
I call my auto-generated select-option subscreen in my PBO with...
call subscreen sca_ordr including sy-repid scr_0121.
and in my PAI with...
call subscreen sca_ordr.
In order to do LOOP AT SCREEN for my system-generated select-option subscreen, I use the AT SELECTION-SCREEN OUTPUT event in which to put my loop.
When I walk thru this in the debugger, I can see it setting INPUT/OUTPUT fields to zero, but when the screen displays, there are no changes to my subscreen.... Fields should be "greyed out" instead they are open for intput.
Doing my best to accurately describe in as few words as possible. Thank you for your ideas!
Dean.

Interface not found in implements-attribute for MXML component

Hi,
I am trying to use the "implements" attribute for an
MXML-component in order to implement an interface from a library
like below (Flex 3). I get the error "Interface IClonable not
found". The compiler does not complain about " import
com.yworks.support.IClonable;", so the library is installed
correctly. I use the library in many places in my project, it just
does not find it in the "implements" tag. How can I fix this
without reimplementing the component in ActionScript?
<?xml version="1.0" encoding="utf-8"?>
<mx:VBox xmlns:mx="
http://www.adobe.com/2006/mxml"
implements="com.yworks.support.IClonable">
<mx:Script>
<![CDATA[
import com.yworks.support.IClonable;
]]>
</mx:Script>
</mx:VBox>

"mavdzee" <[email protected]> wrote in
message
news:gldjg8$js8$[email protected]..
> Hi,
>
> I am trying to use the "implements" attribute for an
MXML-component in
> order
> to implement an interface from a library like below
(Flex 3). I get the
> error
> "Interface IClonable not found". The compiler does not
complain about "
> import
> com.yworks.support.IClonable;", so the library is
installed correctly. I
> use
> the library in many places in my project, it just does
not find it in the
> "implements" tag. How can I fix this without
reimplementing the component
> in
> ActionScript?
>
>
> <?xml version="1.0" encoding="utf-8"?>
> <mx:VBox xmlns:mx="
http://www.adobe.com/2006/mxml"
> implements="com.yworks.support.IClonable">
>
> <mx:Script>
> <![CDATA[
>
> import com.yworks.support.IClonable;
>
> ]]>
> </mx:Script>
>
> </mx:VBox>
I don't see anything where you're actually _implementing_ the
interface, but
I'd expect to see a different error if that's the problem.
Still, I'd go
ahead and implement the properties and methods in the
interface, just to
make sure.
HTH;
Amy

Attribute can be a field for selection screen

Hi,
For 0employee i have made a attribute as organization unit in a report,so org unit is attribute for 0employee and now my requirement is that i want that organization unit to be in selection screen for Bex reporting so that the user can choose the org unit from the selection screen only.

Hi,
If you need to include organization unit, which is a attribute of 0employee, in you report, you need to perform the below steps.
1. In the 0EMPLOYEE characteristic Attribute tab, make organization unit as a Navigational attribute.
2. In the InfoProviders on which the query is created, you need to select organization unit as a navigational attribute.
3. If your report is created on a multiprovider, you need to select organization unit as a navigational attribute in Multiprovider also and create assignment for it.
ex: If your report is based on a multiprovider, which is created on a Cube and cube has a ODS below it, you need to perform above steps at all levels.
You will now be able to see the organization unit as a characteristic in report, just pull it and create a variable.
Please let me know if you need any more information.
Regards,
Pankaj

Using navigational attributes in selection for a forecast profile

Hello All,
I could understand that the forecasting can be done on navigational attributes.
But when I goto transaction /SAPAPO/MSDP_FCST2, I could not create a selection on navigational attribute.
Because I could not see the navigational attribute field in the selection screen for selection criteria/profile creation.
Does anyone have any idea of how to do this?
Also I saw the method SEL_CHANGE of BADI /SAPAPO/SDP_FCST5. But the documentation is confusing, since it says that using this method, we could delete the navigational attributes from the selection condition. Could any one suggest me how to use this BADI if I cannot create a selection with navigational attribute?
Thanks,
Suresh

Hi Sunitha,
Thanks a ton for your reply.
The real problem is the OSS note is confusing.
OSS Note for this method says "This method can be used to change the selection to be stored in
in the generated selection table. Navigation attributes can be removed, such as the function of assigning a forecast
profile to the selection can also be allowed for selections with navigation attribute without a basic characteristic."
I am really confused what it says.
If we can't create a navigational attribute for a selection, how could we delete it from a selection?
Thanks,
Suresh

Af:treeTable component: API to return list of expanded nodes?

Hi,
In my UI design, I am using a tree table (af:treeTable component). Does the framework support API to return (at any given time) a list of all expanded nodes?
I realize that I can build logic to 1. return the currently selected node, then 2. query up all of the child nodes of this selected node. However, I'm wondering if, say at a particular instant, multiple nodes have been expanded, and I need a list of all of these nodes for every level in the tree table?
Thanks in advance,
Monica

Hi John,
I am using 11g. From the javadoc, I see that getDisclosedRowKeys() returns "set of disclosed rows for [tree-table] component" and "each entry in the set is a rowKey."
What exactly is the definition of a "disclosed row"? I'm guessing this means any & all rows shown from UI, which would return all rows (including parent nodes of newly expanded nodes)?
Is there a way to return all child nodes (newly displayed rows) of expanded nodes? To clarify, I'm trying to gather rows level by level. If a node has been expanded at level n, I would like to get a new list of nodes at level (n+1).
Thanks,
Monica

Composite component attribute scope

I'm implementing a master-detail screen on bicycles are shown for the bicycle category selected. When the user selects a bicycle category in the selectOneMenu, the change request is handled using ajax and the new list of bicycles is displayed.
<cc:interface>
     <cc:attribute name="categoryHolder" required="true">
          <cc:attribute name="selectedCategory" />
     </cc:attribute>
     <cc:attribute name="onSelectCategory"
          method-signature="void action()" required="false" />
     <cc:attribute name="showAllOption" required="false"
          default="#{false}" />
     <cc:attribute name="onChangeRender" required="false" default="@form" />
     <cc:attribute name="rendered" required="false" default="#{true}" />
</cc:interface>
<cc:implementation>
     <h:selectOneMenu value="#{cc.attrs.categoryHolder.selectedCategory}"
          rendered="#{cc.attrs.rendered}">
          <f:selectItem itemLabel="All" itemValue="#{null}" noSelectionOption="#{true}" />
          <f:selectItems
               value="#{bicycleCategoryListUiComponent.bicycleCategories}"
               var="bicycleCategory" itemLabel="#{bicycleCategory.name}"
               itemValue="#{bicycleCategory}" />
          <f:ajax event="change" render="#{onChangeRender}" execute="#{cc.attrs.categoryHolder.check()}" />
     </h:selectOneMenu>
</cc:implementation>I call the component like this:
          <component:bicycleCategoryList
               categoryHolder="#{selectBicyclePageBean}" onChangeRender="@form" />However, when I select a category I get the following error message:
serverError: class javax.faces.component.UpdateModelException /resources/component/bicycleCategoryList.xhtml @32,35 value="#{cc.attrs.categoryHolder.selectedCategory}": java.lang.NullPointerException
It seems like #{cc.attrs.categoryHolder} has run out of scope and this isn't available anymore.Therefore I'm wondering how I can manipulate the scope of composite component attributes? JSF 2 has elegent scopes for managed beans, but I could not find anything about this topic. When there is some other solution, also please enlighten me.
Thanks in advance!

Did you find a solution to your problem? I too am trying to do something similar but rather than have an onChangeRender attribute, I was trying to find a way to nest <f:ajax> inside the call to the custom component. Using your code as an example, I was trying to do the following:
<component:bicycleCategoryList categoryHolder="#{selectBicyclePageBean}">
    <f:ajax event="someCustomEvent" render="@form"/>
</component:bicycleCategoryList>However I get the following exception:
<f:ajax> Error: enclosing composite component does not support event someCustomEventIn the FacesComponent, I did implement ClientBehaviorHolder. The someCustomEvent would be fired after an internal <f:ajax> is called. For example:
<f:ajax onevent="handle_onevent"/>Then:
function handle_onevent(data) {
     if (data.status == "success") {
          var evt = document.createEvent("Events")
          evt.initEvent("someCustomEvent", true, true);
          this.dispatchEvent(evt);
}Any help would be very appreciated. Thanks!

Using Static Variable against Context Attribute for Holding IWDView

Dear Friends,
I have a method which is in another DC which has a parameter of the type IWDView. In my view, I will have an action which will call the method in another component by passing the value for the view parameter. Here, I can achieve this in 2 types. One is - I declare a static variable and assign the wdDoModifyView's view as parameter value and I can pass this variable as parameter whenever calling that method or the second way - create an attribute and assign the same wdDoModifyView's view parameter as its value. Whenever I call this method, I can pass this attribute as parameter. What is the difference between these two types of holding the value since I am storing the same value i.e., wdDoModifyView's view parameter. But when I trigger the action from different user sessions, the first type of code (using static variable) prints the same value in both the sessions for view.hashCode() and View.toString(), but the same is printing the different values when I pass the attribute which holds the view parameter.
Clarification on this is highly appreciated
The problem I face is when I use static variable to get the view instance and export the data using the UI element's id, the data belonging to different user sessions is mixed up where as when I use Context Attribute, the same problem doesn't arise. I want to know the reason why it is so. Is there any other place or way where I can get the current view instance of each session instead of wdDoModifyView?

Hi Sujai ,
As you have specified the problem that we face when we use static attributes, when end users are using the application .
Static means i have n number of objects but the static variable value will remain same every where.
when it is context attribute for every object i.e nth object you have a nth context attribute i mean nth copy of the context attribute.
so every user has a unique Iview parameter , when context is used and
when static is used , assume you have userA , his iview is set this intially and u have another user B , when he is using , since the variable is static and when you access this variable you will get the value of userA.
Regards
Govardan Raj

Urgent: How to Remove assignment of a marketing attribute for an BP

Hi Guys,
In my project we are maintaining two marketing attributes for all the business partners.
But there is a need now based on some condition we want to remove one of the assignment for the BP (I.e which ever BP matching the condition)..
I dont want to remove this manually using the transaction code..
Is there any function module to remove the assignment of the marketing attribute for the BP.
Would appreciate an early reply...Since it is very urgent...
Regards,
Sundar

HI Sundar you should follow the following steps.
1. Create a target group in the segment builder selecting all the business partners that meet your criteria.
2. Go to the Expert tools (transaction CRMD_MKT_TOOLS)
3. Select the Deletion of an Attribute for All BP Assignments to a Target Group option.
4. enter in the name of your target group, the attribute set and attribute you want to remove.
Nima

How to restrict data for selection

Hi, folk,
I've faced with the following issue.
I have set of items. There are, for example, income items and expense items.
Items are distinguished by value of attribute.
According to business process, planning for income and expense items is quite different. Due to this reason I've created two planning folders to process ones.
Item was placed into header of planning format.
Before planning I should select item. More over, for income planning I should select item from income subset.
So, how to based on value of attribute I can restrict items for selection in the planning folder.

Easier impossible,
Rather than using a variable of type attribute I would use an variable of type exit.
The exit returns the full list of item in income or expense. (This depends on another variable, that could be a simple digit base or based on some other infoobject).
The variable should be assigned to your level and also available in the planning folder for selection.
The user will see the full list values and select the one he nedes to plan.
I hope it's clear.
Cheers,
Alberto

JDeveloper 11.1.2.3, ADF Faces: need declarative component idea for table

Some background:
I'm trying to create a reusable toolbar for standard af:table behavior, see screen shot
http://wesfang.files.wordpress.com/2013/05/dc.jpg
I got the idea from the from using documentation Frank has published in the past
1. http://www.oracle.com/technetwork/developer-tools/adf/learnmore/001-access-declarative-comp-attr-169113.pdf
2. Adding a new row programatically
The consuming subsystem's page passes in a "MyPageBean" which is a subclass of a "ArchBean" where all actionlistener operations are defined. The idea here is to minimize developer customization when using this component.
... <f:facet name="toolbar">             <af:toolbar id="t2">                 <mskcc:basicTransactionToolbar id="btt1" pageBean="#{MyPageBean}" tableId="t1"/>             </af:toolbar> </f:facet> ...
The table within the consuming page is by default dropped off as a "editable" table. The developer needs to further modify the "disable" attribute to true for all the input fields and command components within the table. I would like to remove this developer step and instead have it in an architectural component. All ideas are welcome.

Ok, finally got it working (sort of)
Using the following method as you suggested:
public void encodeChildren(FacesContext fc){
        try {
            super.encodeChildren(fc);
            RichTable table =
                (RichTable)ADFFacesUtil.findComponentInRoot((String)this.getAttributes().get("tableId"));
            lockUnlockTable(table); //method for toggling disable attribute for all command and input components
        } catch (IOException e) {
            e.printStackTrace();
}Now the strange problem I encountered is that the encode methods are not called if the declarative component is defined within a panelCollection's f:facet-toolbar like below:
<f:facet name="toolbar">
                    <mskcc:basicTransactionToolbar id="btt1" tableId="t1" pageBean="#{TestBean}"/>
</f:facet>Also the above code has to be manually created because the design time editor does not allow me to drop off the dc within the toolbar facet (even though the dc is a toolbar!)
Instead, If I move the dc outside the panelcollection, then the encode methods are invoked and the desired enable/disable behavior is correctly displayed.

How to create a attribute for a table

I am created a table with four columns.
How to create a attribute for each column.........

Hi Cranjith Kumar,
First Create a node for ur table.In that give your table name in the dictionary structure then select option add attributes from the structure that will display the fields there u can select the fields then automatically attributes for ur table will be created in the context.
Reward points if useful.
Edited by: srilalitha yerramsetti on Jun 18, 2008 3:23 PM

Looking for a reference manual that actually describes in detail all attributes for a command

I am using CS5. I am teaching myself Photoshop using their book, "Classroom in a book".
Thought the lessons, they will suggest specific setting for command attributes without describing exacting what these values mean.. For example, on page 88 they give the student specific settings for the Refine Edge dialog bog under the Quick Selection tool. They say, "To prepare the edge for a drop shadow, set Smooth to 24, Feather to 0.5, Contrast to 12, and Shift Edge to -21". Note: I am calling things like Smooth, Feather, Contrast, etc command attributes.
My question is not about this specific example, but all these attribute values for all the commands. For example, what does Shift Edge really do when negative or positive. My question is: does a reference, either a book, pdf, or a non-Adobe product (probably a book) exist that actually explains when each attribute actually does for every command? Basically looking for a boring detailed reference guide so when I am using a specific command, I can read about the attributes for the specific command and understand what the values really mean and not guess my trial and error.
Thanks in Advance,
LouF

Lou Fuchs wrote:
For example, I just happen to have my book open to page 113 and it is showing me (at the bottom of the page) the dialog box for Layer Style. I was hoping for a reference manual that explains every option in the that dialog box in detail and tells you what each option means and how it effects the image.
I hope this clarifies what I am looking for.
Here's a little snippet from the info about Layer Styles in the Adobe manual.
Layer style options
To the top
Altitude For the Bevel and Emboss effect, sets the height of the light source. A setting of 0 is equivalent to ground level, 90 is directly above the layer. Angle Determines the lighting angle at which the effect is applied to the layer. You can drag in the document window to adjust the angle of a Drop Shadow, Inner Shadow, or Satin effect.
Anti-alias Blends the edge pixels of a contour or gloss contour. This option is most useful on small shadows with complicated contours. Blend Mode Determines how the layer style blends with the underlying layers, which may or may not include the active layer. For example, an inner shadow blends with the active layer because the effect is drawn on top of that layer, but a drop shadow blends only with the layers beneath the active layer. In most cases, the default mode for each effect produces the best results. See Blending modes. Choke Shrinks the boundaries of the matte of an Inner Shadow or Inner Glow prior to blurring. Color Specifies the color of a shadow, glow, or highlight. You can click the color box and choose a color. Contour With solid-color glows, Contour allows you to create rings of transparency. With gradient-filled glows, Contour allows you to create variations in the repetition of the gradient color and opacity. In beveling and embossing, Contour allows you to sculpt the ridges, valleys, and bumps that are shaded in the embossing process. With shadows, Contour allows you to specify the fade. For more information, see Modify layer effects with contours. Distance Specifies the offset distance for a shadow or satin effect. You can drag in the document window to adjust the offset distance. Depth Specifies the depth of a bevel. It also specifies the depth of a pattern. Use Global Light This setting allows you to set one “master” lighting angle that is then available in all the layer effects that use shading: Drop Shadow, Inner Shadow, and Bevel and Emboss. In any of these effects, if Use Global Light is selected and you set a lighting angle, that angle becomes the global lighting angle. Any other effect that has Use Global Light selected automatically inherits the same angle setting. If Use Global Light is deselected, the lighting angle you set is “local” and applies only to that effect. You can also set the global lighting angle by choosing Layer Style > Global Light. Gloss Contour Creates a glossy, metallic appearance. Gloss Contour is applied after shading a bevel or emboss. Gradient Specifies the gradient of a layer effect. Click the gradient to display the Gradient Editor, or click the inverted arrow and choose a gradient from the pop-up panel. You can edit a gradient or create a new gradient using the Gradient Editor. You can edit the color or opacity in the Gradient Overlay panel the same way you edit them in the Gradient Editor. For some effects, you can specify additional gradient options. Reverse flips the orientation of the gradient, Align With Layer uses the bounding box of the layer to calculate the gradient fill, and Scale scales the application of the gradient. You can also move the center of the gradient by clicking and dragging in the image window. Style specifies the shape of the gradient. Highlight or Shadow Mode Specifies the blending mode of a bevel or emboss highlight or shadow. Jitter Varies the application of a gradient’s color and opacity. Layer Knocks Out Drop Shadow Controls the drop shadow’s visibility in a semitransparent layer. Noise Specifies the number of random elements in the opacity of a glow or shadow. Enter a value or drag the slider. Opacity Sets the opacity of the layer effect. Enter a value or drag the slider. Pattern Specifies the pattern of a layer effect. Click the pop-up panel and choose a pattern. Click the New Preset button to create a new preset pattern based on the current settings. Click Snap To Origin to make the origin of the pattern the same as the origin of the document (when Link With Layer is selected), or to place the origin at the upper-left corner of the layer (if Link With Layer is deselected). Select Link With Layer if you want the pattern to move along with the layer as the layer moves. Drag the Scale slider or enter a value to specify the size of the pattern. Drag a pattern to position it in the layer; reset the position by using the Snap To Origin button. The Pattern option is not available if no patterns are loaded. Position Specifies the position of a stroke effect as Outside, Inside, or Center. Range Controls which portion or range of the glow is targeted for the contour. Size Specifies the radius and size of blur or the size of the shadow. Soften Blurs the results of shading to reduce unwanted artifacts. Source Specifies the source for an inner glow. Choose Center to apply a glow that emanates from the center of the layer’s content, or Edge toapply a glow that emanates from the inside edges of the layer’s content. Spread Expands the boundaries of the matte prior to blurring.
Style Specifies the style of a bevel: Inner Bevel creates a bevel on the inside edges of the layer contents; Outer Bevel creates a bevel on the outside edges of the layer contents; Emboss simulates the effect of embossing the layer contents against the underlying layers; Pillow Emboss simulates the effect of stamping the edges of the layer contents into the underlying layers; and Stroke Emboss confines embossing to the boundaries of a stroke effect applied to the layer. (The Stroke Emboss effect is not visible if no stroke is applied to the layer.)
Technique Smooth, Chisel Hard, and Chisel Soft are available for bevel and emboss effects; Softer and Precise apply to Inner Glow and Outer Glow effects.
Smooth Blurs the edges of a matte slightly and is useful for all types of mattes, whether their edges are soft or hard. It does not preserve detailed features at larger sizes. Chisel Hard Uses a distance measurement technique and is primarily useful on hard-edged mattes from anti-aliased shapes such as type. It preserves detailed features better than the Smooth technique.
Chisel Soft Uses a modified distance measurement technique and, although not as accurate as Chisel Hard, is more useful on a larger range of mattes. It preserves features better than the Smooth technique. Softer Applies a blur and is useful on all types of mattes, whether their edges are soft or hard. At larger sizes, Softer does not preserve detailed features.
Precise Uses a distance measurement technique to create a glow and is primarily useful on hard-edged mattes from anti-aliased shapes
such as type. It preserves features better than the Softer technique. Texture Applies a texture. Use Scale to scale the size of the texture. Select Link With Layer if you want the texture to move along with the layer as the layer moves. Invert inverts the texture. Depth varies the degree and direction (up/down) to which the texturing is applied. Snap To Origin makes the origin of the pattern the same as the origin of the document (if Link With Layer is deselected) or places the origin in the upper-left corner of the layer (if Link With Layer is selected). Drag the texture to position it in the layer.

ABAP: dynamic context node + attribute for DROP_DOWN_BY_KEY

Hello,
I need to create a Node with attributes dynamically and than assign it to a DROP_DOW_BY_KEY element in ABAP.
I create drop down this way:
drop_down_figure = cl_wd_dropdown_by_key=>new_dropdown_by_key( bind_selected_key = 'REPOSITORY.FIGURES' on_select = 'GET_OPERATOR' ).
cl_wd_grid_data=>new_grid_data( element = drop_down_figure ).
ui_container->add_child( drop_down_figure ).
However, here I bind to REPOSITORY.FIGURES. Instead of doing this I need to bind it to an attribute that I create.
I can access wd_context but I am not sure how to create a node in wd_context, then attribute for that node that will contain items for drop down.
bind_selected_key is type of String. If I create a node with attribute how do I cast it to a String so I can pass it to a constructor of a drop down?
Thank you.

Hi Georgy,
There is a 3 - series weblog for this.
The first one is:
/people/thomas.szcs/blog/2005/12/28/dynamic-programming-in-web-dynpro-abap--introduction-and-part-i-understanding-ui-elements
The following are the the general steps for creating a node and table where table name is input by the user:
DATA:
UI Elements
    group_1       TYPE REF TO cl_wd_uielement_container,
    new_tab       TYPE REF TO cl_wd_table,
Context Nodes
    dyn_node      TYPE REF TO if_wd_context_node,
    tabname_node TYPE REF TO if_wd_context_node,
Node Info
    rootnode_info TYPE REF TO if_wd_context_node_info,
Data Reference (for internal table)
    stru_tab      TYPE REF TO data,
String (for table name)
    tablename     TYPE string.
FIELD-SYMBOLS:
    <tab> TYPE table.
1) * get node info of context root node
rootnode_info = wd_context->get_node_info( ).
2) * create sub node named TEST1 of structure (tablename)
cl_wd_dynamic_tool=>create_nodeinfo_from_struct(
    parent_info = rootnode_info
    node_name = tablename
    structure_name = tablename
    is_multiple = abap_true ).
3) * get instance of new node
dyn_node = wd_context->get_child_node( name = tablename ).
4) ***** create new UI element table *******************************************************
new_tab = cl_wd_dynamic_tool=>create_table_from_node(
ui_parent = group_1
table_id = 'TESTTAB'
node      = dyn_node ).
5) ***** fill context node with data *******************************************************
create internal table of (tabletype)
CREATE DATA stru_tab TYPE TABLE OF (tablename).
ASSIGN stru_tab->* TO <tab>.
Get table content
SELECT * FROM (tablename) INTO CORRESPONDING FIELDS OF TABLE <tab>.
Bind internal table to context node.
dyn_node->bind_table( <tab> ).
Regards,
Srini.

Navigational attribute in selection screen gives no applicable data

Hi Gurus
In the report i am using the navigational attribute in the selection screen.e.g Brand (attribute of material)
My problem is whenevr i enter value in the navigational attribute (brand) in the selection screen and execute its says no data found.
If i do not fill this parameter and fill only the parent attribute (material) in the selection screen , then i can see the results and from its properties (drilling down )i can see the values of brand .
If the values of brand exist why via selection screen its not giving vales, However Via material i can drill down and see brand values.
I have done all the necessary steps to make this attribute as navigational.
On top of this i have this same navigation attributes as one of the characterisitc in the cube.
Thanks
DD

Hello,
I've the same problem... for new nav. attributes for 0Material.
Settings for nav. attibutes in BEx Q.D. are OK.
But in BEx Analyzer:
1- not display all values for this attributes. Some values are displayed, some don't.
I try display it with and without selection screen. The result is the same.
2- I try to display (normal) attributes - not nav. In this case everything is OK.
But I've 2 columns: normal attribute for all values and nav. attribute only with some values...
(the query is something like: 0Material + 0Material_NOTnav_attr + 0Material_NOTnav_attr)
It isn't a normal...
I don't know... Maybe it's depend of the time?
I can't clear all master data for 0Material, because they're used in some cubes. I had old characteristic without nav. attr. but with master data. I added nav. attr. in 0Material and activated it. Next I load master data (full method). Then I added nav. attr. in infocube, activated it, delete and load data into the cube (Init + Delta).
If I display data for the cube in RSA1, I can see nav. attr. for all records. I can't see it in BEx Analyzer...
Can U explain it?
Thx,
MSzN

TreeTable Component - attributes for $selected[*]

Similar Messages

Maybe you are looking for