AM_ call to update screen field does not update the field

Question

Hello, 
 I am using a simple piece of code to display a field from another screen in Manual Matching (LETTRAGE). When placed in an infobox, the data displays correctly, but when trying to Affzo the field on the screen, nothing is displayed. 
 When the BP number is entered ([M:LTR]BPR) an info box displaying the text from a custom field in [F:BPR] (BPARTNER) called ZMATCHN is displayed: 
 
 However, the field which I added to LETTRAGE called ZMATCHN ([M:LTR]ZMATCHN) does not update. Does it need to be in a table? (See "Matching Notes" is blank to the right. It does not display "test") 
 
 $ACTION
Case ACTION
 When default
Endcase
Return

Subprog AM_BPR(VALEUR)
Variable Char VALEUR()
If VALEUR = 'EE9391'
read [F:BPR]BPR0 = VALEUR
If fstat = 0
Infbox ([F:BPR]ZMATCHN)
[M:LTR]ZMATCHN = [F:BPR]ZMATCHN
Affzo [M:LTR]ZMATCHN
Endif
Endif
End

Zoey Mattison · Accepted Answer

Regard Hulsbos NMA I've figured out a workaround just now. I think the finicky-ness of this is due to the screen itself. I tried a simple trick of changing the default field of [F:LTR]ZMATCHN to be [F:BPR]ZMATCHN. After you hit enter on the BPR field in LETTRAGE to display records to be matched, the Matching Notes field updates and shows the notes accordingly, and updates with every BP you enter into the field. The field does not update at all before clicking search when you use [F:LTR]ZMATCHN = [F:BPR]ZMATCHN in the AM_BPR SPE code. However, having the read function allows it to update the default value every time. Here is the final set up to get this working: Step 1: Update the Table Add a new field into the BPARTNER table of type A, length 250. For this example, I've called it ZMATCHN Validate the table Step 2: Add the necessary screen fields In BPR1, add a field called ZMATCHN, type A, length 250, Graphical Object multiline text. (I set it to 5 lines and 40 columns, type Text File). In LETTRAGE, add a field called ZMATCHN, and set it up identically to the field from BPR1. Additionally, set the default value of THIS field to be [F:BPR]ZMATCHN In LETTRAGE, add a AFTER CHANGE action to the BPR field - SPE, executional Always, deactivation None. This will allow us to capture the BPR value after entry Validate both screens. Step 3: Add SPE code to read the BPARTNER table from LETTRAGE Navigate to the script editor and open SPELTR You will notice a section automatically added called AM_BPR Add the following code to open and read the BPRARTNER table using the BPR field value as the key (note: no updating of the ZMATCHN field is required here): $ACTION Case ACTION When default Endcase Return Subprog AM_BPR(VALEUR) Variable Char VALEUR() if !clalev([F:BPR]) : Local File BPARTNER[F:BPR] : Endif If [F:BPR]BPRNUM <> VALEUR Read [F:BPR]BPR0 = VALEUR IF fstat <> [V]CTS_AOK : End : Endif Endif End Compile your code Step 4: Test Open Manual Matching, input your AR code and then in BP field, input your BP code. You can then use the "Jump to" button to jump to the BP setup of this code, and enter any notes you may need into your ZMATCH field that we added earlier Save your BP document, and click close page. Hit enter or click "search" in manual matching. The update will now display the appropriate matching notes from the BPARTNER table in the ZMATCHN field of the LETTRAGE screen:

Sage X3

AM_ call to update screen field does not update the field

Top Replies

COMMUNITY

COMPANY

PARTNERS

SUPPORT & TRAINING