Skip to main content

Comments

4 comments

  • Official comment
    Apollo Cherniak

    I figured it out...I didn't understand how to use the $[B1DASHBOARDVALUE.STRING], but that's all I was missing.  Rename the field in the SQL, and it seems that it knows that's the field you want to return with the $[B1DASHBOARDVALUE.STRING].  I guess you could only capture a single field though to populate in the new window, in the event you wanted to open a window that asked for both WhsCode AND ItemCode for example.  Works for me for now anyway.  Thanks Dave.

     

  • Dave Gutman

    Hi Apollo, 

    The easiest way that I've seen is to create universal function for the non-SAP screen.  If the target is an SAP UDO then use a Macro type with the Activate() command.  If it is outside of SAP, then you can use type of External Launcher.  I haven't tried using @STORE variables in the Arguments field. 

    Dave Gutman

  • Apollo Cherniak

    Thanks Dave Gutman, that makes sense...but once I have the screen open, how does it know which record to open?  For example, I want to open the Batch Details screen.  My grid outputs a list of batch numbers along with expiration date.  How do I tell it to open the batch details for the specific record that I double-clicked on?

  • Dave Gutman

    That's the part I haven't done before.  Suggest you try using the @STORE variables on the Arguments field on the External Launcher. 

    If you're doing the Macro with the Activate function then I think you'll have more control over the screen from within the UF.  This depends on how the SAP-based screen that you're accessing via the Activate() command is written.  It may respond to other macro commands that follow the Activate() command and may let you drive it into the target record.  

Please sign in to leave a comment.