Hello Alberto, The Solomon Object model is designed to manipulate Microsoft Dynamics SL applications through automation. If the user wants to do the interaction with Material Issues screen, The Solomon Object model won’t allow you to do that. Did you try use the StartApplication function instead of StartAppandAutomate? Or else you can use the CallApplicWait & ApplSetParmValue & ApplGetParmValue function to achieve the user control over material issues screen The following example illustrates how to pass parameters to a Microsoft SL SDK application and custom BSL code at the same time and avoid conflicts between the two. Code in the calling application: Call ApplSetParmValue (PRMSECTION_VBRDT, "Batch Nbr", "000001") Call ApplSetParmValue (PRMSECTION_VBRDT, "Document Nbr", "123456") Call ApplSetParmValue (PRMSECTION_BSL, "Example Parm", "Example Parameter To BSL Code") 'Call another Microsoft Dynamics SL application CallApplicWait ( "Microsoft Dynamics SL APP", "") Code in the standard Microsoft SL SDK application (that is, non-customization code) receiving the standard parameters. Dim Parm_BatchNbr As String Dim Parm_DocumentNbr As String Parm_BatchNbr = ApplGetParmValue (PRMSECTION_VBRDT, "Batch Nbr" Parm_DocumentNbr = ApplGetParmValue (PRMSECTION_VBRDT, "Document Nbr") Basic Script code, overlaying the standard Microsoft SL SDK application, designed to retrieve custom parameters: Dim Parm_CustomParm As String Parm_CustomParm = ApplGetParmValue (PRMSECTION_BSL, "Example Parm") You can refer this concept in BasiScriptcLanguage.pdf which can be found under user_guides folder of Solomon Root folder. Hope this explains.
↧