LAE

Welcome to the LAE community!  Please feel free to start a discussion in the discussion tab or join in a conversation.

Discussions

Members

Resources

Events

 View Only
  • 1.  Feature request: GUI for emit

    Employee
    Posted 03-06-2012 03:22

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: erno

    Hi all,

    we are using BRE mostly with raw SAP tables that can have 50 different columns, from which only 10-20 are used. It would be very convenient for us if there was a GUI for selecting which fields are emitted and in which order.

    One potential place for such feature would be in Node -> Status -> Fields -list.

    Does this feature request sound reasonable?

    Best,
    Erno


  • 2.  RE: Feature request: GUI for emit

    Employee
    Posted 03-08-2012 08:47

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: rboccuzzi

    Have you looked at the FieldHelper functionality? If you go into BRE's help menu, choose BRE Help, and then under the miscellaneous BRE controls, there is a Field Helper section, that might have what you are looking for.

    Cheers
    Rich


  • 3.  RE: Feature request: GUI for emit

    Employee
    Posted 03-29-2012 04:01

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: erno

    That fieldhelper feature looks promising! After adding fields to different groups how does 'emit' function or outputting work? Is there a tutorial available?

    Many thanks,
    Erno


  • 4.  RE: Feature request: GUI for emit

    Employee
    Posted 03-30-2012 09:48

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: rboccuzzi

    There is some help on it. It should be in the Field Helper section, where it talks about
    {{^output#FieldHelperParameter^}}
    and
    {{^rename#FieldHelperParameter^}}
    after this line "When the Field Helper widget has been appropriately filled in, it can be used in BRAINscript parameters via substitution to generate the appropriate BRAINscript code automatically. The following substitutions are allowed:"

    So you would create a FieldHelper type parameter, say you called it "foo", then you would "use" it in a Script parameter, in a Filter, for example, like this:
    {{^output#foo^}}
    to output all the fields in the 1,2 or 3 group

    Cheers
    Rich


  • 5.  RE: Feature request: GUI for emit

    Employee
    Posted 04-01-2012 08:07

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: erno

    Got it finally, thanks!


  • 6.  RE: Feature request: GUI for emit

    Employee
    Posted 04-04-2012 11:48

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: ejones

    FieldHelper is probably the quickest to use once you understand and can remember or quickly find the parameters.

    Another possible option is to use the "Data Analyzer" node which will create sample BrainScript code for you that you can copy and paste into some other node type.

    To use it, put the "Data Analyzer" node into your graph which is found under "Profiling and Patterns". Connect the input to the output of the node containing the large number of fields. Execute it. Then open the middle output in the BRD viewer. Notice that the very last field contains BrainScript. So highlight and copy that column of data and paste it into maybe the Script parameter of a Filter node. Then you can quickly modify the code to emit the fields desired in the format desired.

    Thanks,
    Ernest


  • 7.  RE: Feature request: GUI for emit

    Employee
    Posted 11-29-2012 04:56

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: aop

    I'm sharing the same trouble with Erno when it comes to defining fields to be displayd in output and affecting the dipslay order when working with data sets with large amount of fields. I think I will also definately need to look into the field helper. Currently I don't yet quite understand the possibilities with it and previously I have had some trouble trying to set it up.

    Just as an idea, maybe the kind of functionality Erno was requesting could be built in the BRD viewer. First of all it would be a very nice feature to be able to drag&drop fields (like in ACL) in the viewer to change their order in addition to the "display as first column" feature currently available. Then there could be a possibility to copy the field order displayed in the viewer as an emit statement ("Copy as emit filter" in somewhat same way as is now possbile with copying examine filter).

    Usual scenario for me is that I would need to force the order of some of the first columns in emit statement for reporting purposes (critical fields as first fields in the output) but would anyway like to display all input fields in the output (often dozens). Would be nice be able to achieve this with the emit statement without the need to define all the fields. I think currently this is not possible?


  • 8.  RE: Feature request: GUI for emit

    Employee
    Posted 11-29-2012 11:08

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: rboccuzzi

    Originally posted by: aop
    					

    Just as an idea, maybe the kind of functionality Erno was requesting could be built in the BRD viewer. First of all it would be a very nice feature to be able to drag&drop fields (like in ACL) in the viewer to change their order in addition to the "display as first column" feature currently available. Then there could be a possibility to copy the field order displayed in the viewer as an emit statement ("Copy as emit filter" in somewhat same way as is now possbile with copying examine filter).
    This is a good idea, I like it. I have captured it as an enhancement request, PR 4393.

    Cheers
    Rich