Skip to Content

Change order of InfoObject attributes in Bex Queries

Hello,

I have a question relating to Bex Queries. When viewing the Characteristics of an InfoObject using the Properties context menu in Portal at runtime, in the Attributes tab for an InfoObject, all "Available Attributes" are sorted alphabetically.

Does anyone know how to change this order so that attributes are listed in a custom sort order?

We have tried experimenting with the "Order for F4 Help" field in RSD1, but the number in that field for a given attribute has no effect on the order attributes appear in at runtime.

Thanks

Scott

Add comment
10|10000 characters needed characters exceeded

  • Thanks William!

    Yes, you're correct. We know how to change attribute order within Query Designer or Bex, but we'd like to re-order the sequence attributes appear in on the Help menu. Some of our dimensions have a large number of attributes, with some more frequently used than others. We'd like to sort them from least to most commonly used.

    Thanks,

    Scott

  • Hmm strange...any chance you can share a screenshot of what you have set up for the attribute display on the info object properties in RSD1? And your info object is active, correct?

  • Hi William,

    Again thanks for the reply.

    Attached are two screen captures. The first is a screenshot of the InfoObject in RSD1. Yes, the InfoObject is active, which you'll see in the screenshot.

    Second, below, is the order attributes appear in in F4 help - you'll notice that it's sorted alpha, based on the text of the attribute. I've also noticed that even dimensions with "0" for the "Order for F4 help" field in RSD1 appear in this list. Our goal is to change the order in the "Available Attributes" menu to a custom sort order.

  • Get RSS Feed

1 Answer

  • Sep 20, 2017 at 09:05 AM

    Hi,

    workaround

    you can defnine it per query (Just per Query) or per MP(just for the queries based upon the MP) or per InfoObject(whole BW landscape)

    Add comment
    10|10000 characters needed characters exceeded

    • I see, thanks. I can see how that might work in some cases, but within our organization, the texts for our attribute names have to be maintained, so I don't think this is the solution unless I misunderstood. Thanks though.