Skip to Content
author's profile photo DEVELOPMENT THEMIS
0
DEVELOPMENT THEMIS

REMOVE_ATTRIBUTE removes all of the attributes

Posted on Apr 18, 2011 at 01:44 PM 37 Views

Hello everyone,

I've coded a WDA which builds a UI dynamically. I'm adding attributes to a context node and removing them whenever the user clicks on a button.

I've realized that in this case all of the attributes assigned to the node are removed. In fact the standard method:

IF_WD_CONTEXT_NODE_INFO~REMOVE_ATTRIBUTE

contains the statement:

 me->invalidate_nodes( )

which appears to invalidate all of the nodes and this is clearly not what I was expecting.

I just wanted to remove the selected attribute through the coding:

node_info->remove_attribute( name = lv_param3 ).

I honestly don't understand why the REMOVE_ATTRIBUTE has got this semantics, it doesn't make much sense to me.

How can I delete a certain attribute without invalidating all the other siblings?

Thank you!

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • Best Answer
    author's profile photo DEVELOPMENT THEMIS
    DEVELOPMENT THEMIS
    Posted on Apr 21, 2011 at 09:01 AM
    2

    I was expecting an alternative to this weird functionality...

    Add a comment
    10|10000 characters needed characters exceeded

    • DEVELOPMENT THEMIS Thomas Jung
      May 04, 2011 at 08:13 PM

      Thank you very much Thomas,

      I wasn't aware of this option.

      However I found an alternative solution. Instead of creating child attributes of a parent node, I've created child nodes (and attributes to them) of the parent node.

      This means that my context contains:

      CONTRACT.COMPANY_CONTACTS.COMPANY_CONTACT_1.COMPANY_CONTACT_1
CONTRACT.COMPANY_CONTACTS.COMPANY_CONTACT_2.COMPANY_CONTACT_3
CONTRACT.COMPANY_CONTACTS.COMPANY_CONTACT_3.COMPANY_CONTACT_3

      and I then invalidate 

      CONTRACT.COMPANY_CONTACTS.COMPANY_CONTACT_X.COMPANY_CONTACT_X

      It works okay.

      Anyway, yours is a more elegant solution. Going to go for it next time. However I still can't figure out why SAP implemented the REMOVE_ATTRIBUTE that way.....?

      Cheers

    Comment on This Answer
  • author's profile photo Former Member
    Former Member
    Posted on Apr 18, 2011 at 04:36 PM
    1

    Hello,

    I hadnt used this before.

    This seems to be standard behavior. I had a look at the documentation at https://cw.sdn.sap.com/cw/docs/DOC-30536.

    REMOVE_ATTRIBUTE

    A dynamic attribute can be deleted again using this method. All nodes (runtime instances are invalidated) that reference to this node info.

    The reason for invalidating the nodes corresponding to the node info could be that all the existing instances would have the reference to the attribute which is getting deleted. That will be invalid information after the attribute is removed. So by invalidating the nodes, all the elements for those nodes will be removed. And we need to create the elements again.

    Hope this helps!

    Best Regards,

    Srilatha

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.