31 Responses to Adding Fields to a Panel and the Customer Extension Table

1. Lode Vlaeminck says:

   2017/01/17 at 23:02

   In which scenario would you advice to use this solution vs a database extension?

   Reply
   • potatoit says:

     2017/01/18 at 07:19

     A database extension? If you mean changing the M3 database tables / adding new tables to the M3 database, then I would council against doing that very strongly – it will come back to bite you.

     The customer extension tables have been provided for the purpose of storing additional data to prevent changes to the structure of the M3 database – though this script only takes advantage of a single field, there are multiple alpha fields, multiple numeric fields which are available in a single record / API call.

     If a record was storing very large numbers of fields for a record then you can split it in to multiple records or you could consider creating your own database outside of M3 and using MWS webservices to manipulate the record.

     Reply
2. Lode Vlaeminck says:

   2017/01/18 at 20:18

   I meant adding extra tables using MAK (M3 adaptation Kit). For instance creating ZITMAS that has the same index as MITMAS but holds additional item master data.

   Reply
   • potatoit says:

     2017/01/18 at 20:34

     Infor created the extension tables to get away from people modifying M3 via MAK. I strongly recommend that people work to get rid of modifications and get to standard M3, it makes support and upgrades far quicker and easier. If people are considering modifications, I will do my best to convince them that this is not the route to go – I’ve seen far too many companies regret their modifications come upgrade or even patch time.

     Infor, like most ERP vendors is moving towards hosting and though Infor have a product where you can bring your mods in to the cloud, it will become harder and more expensive as they push everyone towards standard multi-tentanted solutions.

     Cheers,
     Scott

     Reply
     • Lode Vlaeminck says:

       2017/01/18 at 20:37

       Oké that’s clear, Thanks!
3. Magnus Tallqvist says:

   2017/01/19 at 21:37

   Please note that in 13.4 there is a Metadata function added to the customer extension fields (CDF). The function is called CMS080 and through that name, description, type etc are maintained for each CDF. Please also note that from 13.4 the metadata entry is mandatory to be able to use the CDF´s

   Reply
   • potatoit says:

     2017/01/20 at 07:13

     Thanks Magnus,

     I gather that this metadata is mandatory if you are using the native M3 functionality to access the data?
     Is there any implications from an upgrade perspective where customers are using the extended toolboxes to display data from the customer extension tables?

     And for peoples reference, you can read about CMS080 in KB: 1824822 and document ID 49129 entitled
     “M3 13.4 – Business Engine Net Change Overview – What s new in detail”

     Reply
4. Magnus Tallqvist says:

   2017/01/21 at 00:15

   Both the API (CUSEXTMI) and the usage in configurable lists requires a corresponding metadata record in CMS080 in order for it to be possible to use the CDF´s. It is a one time activity to add the records into CMS080 at an upgrade so it is not a bit task but you need to be aware. Secondly it gives a number of advantages like field descriptions, validation of values etc. Through the usage of the text (classic F6) in CMS080 you can also get into a sort of user defined help text through the script (text ID is included in the CMS080MI transaction).

   Reply
   • potatoit says:

     2017/01/23 at 09:09

     Thank you for the explanation Magnus.

     Reply
5. yvon says:

   2017/03/03 at 00:32

   Hi, good post.
   I have an error when launching the script

   DEBUG: Set Controls Position
   DEBUG: +– Control:
   DEBUG: +—- Column: 50
   DEBUG: +—- Row: 6
   ERROR: TypeError: Type mismatch

   an idea please
   Thank

   Reply
   • potatoit says:

     2017/03/03 at 06:09

     Hi Yvon,

     check the script arguments, things like the label column, widths etc have to be numbers – if you’ve missed a field or a comma then you’ll probably get a similar message.

     The other thing that may do it is the “read only key field”, it must be a TextBox and it should be a TextBox that will toggle between enabled and disabled depending on whether the user is changing or displaying the data in the panel.

     Cheers,
     Scott

     Reply
     • yvon says:

       2017/03/03 at 19:34

       Hi Scott,

       I dont understand, I have a copy paste of your arguments and on the MMS001 / E:

       My Label, 40,100,51,100.1, MMITNE, SACTEST, WEITNO

       I dont understand the second problem you. What should I do please

       thank you
       Cheers
       Yvon
     • potatoit says:

       2017/03/03 at 19:54

       In the arguments you’ve pasted, you have

       My Label, 40,100,51,100.1, MMITNE, SACTEST, WEITNO

       The arguments in my article are different
       My Label,40,100,51,100,1,MMITNE,SACTEST,WEITNO

       Note that you have
       100.1, MMITNE
       rather than
       100,1,MMITNE

       Cheers,
       Scott
     • yvon says:

       2017/03/03 at 20:20

       I’m sorry,

       In fact I have

       My Label,40,100,51,100,1,MMITNE,SACTEST,WEITNO

       the message is :

       DEBUG: Set Controls Position
       DEBUG: +– Control:
       DEBUG: +—- Column: 40
       DEBUG: +—- Row: 1
       ERROR: TypeError: Type mismatch

       I have that letter M that appears

       Help thank
     • potatoit says:

       2017/03/03 at 20:35

       Using those arguments on MMS001/E works without error in my environment.

       Are you using those arguments on MMS001/E?
       What version of Smart Office (including the build)?

       Cheers,
       Scott
   • rbottern says:

     2017/05/13 at 07:10

     Hi Yvon,
     I had the same error, and i turned out to be related to localisations due to some users having their PC set as Decimal Comma instead of Decimal points and the calculation below caused a fractional value with a decimal point that fails on some machines.
     textBoxColumnSpan = gControlWidth / gridColumnWidth;
     labeltextBoxColumnSpan = gLabelWidth / gridColumnWidth;
     ….
     Grid.SetColumnSpan(gTextBox, textBoxColumnSpan);
     Grid.SetColumnSpan(label, labeltextBoxColumnSpan);

     Solution was to change the calculation like this (to round up to next Integer):
     textBoxColumnSpan = Math.ceil(gControlWidth / gridColumnWidth);
     labeltextBoxColumnSpan = Math.ceil(gLabelWidth / gridColumnWidth);

     Hope this helps.
     Rene

     Reply
     • yvon says:

       2017/05/17 at 01:33

       Thank you I will watch when I have a moment.
     • Hari Prasad says:

       2019/04/12 at 22:14

       This is really helpful.When setting the Grid.SetColumnSpan(gTextBox, textBoxColumnSpan) value getting type cast issue. After applying the fix it’s working fine.
       (textBoxColumnSpan should be int value.)
6. yvon says:

   2017/03/03 at 20:56

   Yes in MMS001/E

   Version : 10.2.1.0.200
   BE 15.1.4 MCP1 – 1514 – 05

   Cheers
   Yvon

   Reply
   • potatoit says:

     2017/03/05 at 18:09

     Hi Yvon,

     please see the comments from Magnus on this article. He mentions that there needs to be a CMS080 entry for the field you’re adding.

     When I get some free time with a 13.4 environment, I’ll take a look at modifying this script so it can automatically generated the info or documenting what needs to be done.

     Cheers,
     Scott

     Reply
     • yvon says:

       2017/03/06 at 19:40

       Hi Scott,

       thank you for your reply. I will look at the CMS080

       Cheers
       Yvon
7. rbottern says:

   2017/05/13 at 07:17

   I have created a “numeric” version of this script as well including field length and decimal point control if someone is interested.
   Also changed the delimiter to “Pipe” to ensure international compatibility.

   /*
   ** Name: AddControl_Num.js
   **
   ** Description:
   ** Adds a Numeric field to a panel the contents of which will be read from/saved to the customer extension tables
   ** Uniqiness is defined by the Nxxx keys which must be associated with numeric textboxes
   ** We also handle situations where we are in display mode by keying off an existing textbox which changes from
   ** read only to editable depending on display/edit
   **
   ** Notes:
   ** we get the keys from the UI at the point we save, this means that if the key textboxes are changable, we may get
   ** not have the expected results, however this may be the expected result
   **
   ** If the user enters a blank value in to our textbox we don’t delete the record, we just save the N096 as 0.0
   **
   ** Don’t use comments in the label text!
   **
   ** Arguments:
   **
   ** ||||||||||||[PK02]|[PK03]|[PK04]|[PK05]|[PK06]|[PK07]|[PK08]
   **
   ** Eg on MMS002/E
   ** My Label|40|100|51|50|1|5|0|MBRESP|SACTEST|N096|WEWHLO|WEITNO
   ** – My Label = the label we will put next to the textbox
   ** – 40 = the grid column the label goes
   ** – 100 = with width of the label
   ** – 51 = the grid column of the textbox
   ** – 100 = width of the textbox
   ** – 1 = the row we will use for the label and textbox
   ** – 10 = Max length of Text
   ** – 0 = Decimals (If 0 then integer), maximum 6 decimals
   ** – MBRESP = the TextBox that will change from being read only and editable depending on whether we display/edit
   ** – SACTEST = the F1FILE field that we will store against in the Customer Extension table (CUGEX1)
   ** – WEITNO = this will be the first and only of our keys
   ** In the CUGEX1 table we will have
   ** F1FILE = SACTEST
   ** F1PK01 =
   ** F1N096 =
   **
   ** Written By: scott.campbell@potatoit.kiwi
   ** Co-Author: Rene Bottern (Based on AddControl.js)
   **
   */

   // Default Operation for MMS002/E
   // Label Text, Label Column, Label Width, Column, Width, Row, MaxLen, Decimals, ReadOnly FieldRef, CMS080 File, CMS080 Field4
   // Operation|0|80|14|40|10|5|0|MBRESP|MITBAL|N196|WEWHLO|WEITNO

   import System;
   import System.Windows;
   import System.Windows.Controls;
   import MForms;

   import Mango.UI.Core;
   import Lawson.M3.MI;

   package MForms.JScript
   {
   class AddControl_Num
   {
   var gDebug = null;
   var gController = null;
   var gContent = null;

   var gTextBox : TextBox = new TextBox();

   // this is the control that we will use to determine if
   // we should be read only
   var gReadOnlyControl = null;
   var gReadOnlyControlName = null;

   var gControlColumn = -1;
   var gControlRow = -1;
   var gControlWidth = -1;
   var gControlMaxLength = -1;
   var gControlDecimals = -1;
   var gLabelColumn = -1;
   var gLabelWidth = -1;
   var gLabelContent = null;

   var gCUGFile = null;
   var gCUGField4 = null;

   // store our TextBoxes here
   var gKeyField1 = null;
   var gKeyField2 = null;
   var gKeyField3 = null;
   var gKeyField4 = null;
   var gKeyField5 = null;
   var gKeyField6 = null;
   var gKeyField7 = null;
   var gKeyField8 = null;

   // have we finished retrieving our value?
   var gRetrieveValue = false;

   public function Init(element: Object, args: Object, controller : Object, debug : Object)
   {
   gController = controller;
   gContent = controller.RenderEngine.Content;
   gDebug = debug;
   try
   {
   if(null != args)
   {
   var argumentArray = args.split(“|”);

   if(null != argumentArray)
   {
   if(argumentArray.length > 10)
   {
   for(var i = 0; i Comma using regex characters to replace ALL instances
   // labeltextBoxColumnSpan = labeltextBoxColumnSpan.replace(“.”,”,”)
   //}
   Grid.SetColumnSpan(gTextBox, textBoxColumnSpan);
   Grid.SetColumnSpan(label, labeltextBoxColumnSpan);
   }

   gTextBox.Height = Configuration.ControlHeight;
   gTextBox.Margin = Configuration.ControlMargin;
   gTextBox.Padding = Configuration.ControlPadding;
   gTextBox.Width = gControlWidth;
   gTextBox.MaxLength = gControlMaxLength;

   setPosition(gTextBox, gControlColumn, gControlRow);
   gContent.Children.Add(gTextBox);

   gTextBox.add_TextChanged(OnTextChanged); //Check for entry of only numeric value
   }

   function OnTextChanged(sender: Object, e: TextChangedEventArgs) {
   if (sender.Text /*validation expression here*/) {
   //gDebug.Debug(gTextBox.Text);
   if(isNumber(gTextBox.Text.substr(gTextBox.Text.length-1)) == false ) gTextBox.Text = gTextBox.Text.substr(0, gTextBox.Text.length – 1);
   } else {
   // invalid
   }
   }

   function isNumber(evt) {
   var charCode = evt.charCodeAt(0);
   //gDebug.Debug(evt.charCodeAt(0));
   if ((charCode >= 48 && charCode 0)
   {
   result = aContent.ColumnDefinitions[0].ActualWidth;
   }
   return(result);
   }

   private function setPosition(aControl, aColumn, aRow)
   {
   if(null != aControl)
   {
   //gDebug.Debug(“Set Controls Position”);
   //gDebug.Debug(” +– Control: ” + aControl.Name);
   //gDebug.Debug(” +—- Column: ” + aColumn);
   //gDebug.Debug(” +—- Row: ” + aRow);
   Grid.SetColumn(aControl, aColumn);
   Grid.SetRow(aControl, aRow);
   }
   }

   private function CUSEXTMI_GetFieldValue(aFile, aPK01, aPK02, aPK03, aPK04, aPK05, aPK06, aPK07, aPK08)
   {
   var request = new MIRequest();
   var inRecord = new MIRecord();

   inRecord[“FILE”] = aFile;
   inRecord[“PK01”] = aPK01;

   if(null != aPK02) inRecord[“PK02”] = aPK02;
   if(null != aPK03) inRecord[“PK03”] = aPK03;
   if(null != aPK04) inRecord[“PK04”] = aPK04;
   if(null != aPK05) inRecord[“PK05”] = aPK05;
   if(null != aPK06) inRecord[“PK06”] = aPK06;
   if(null != aPK07) inRecord[“PK07”] = aPK07;
   if(null != aPK08) inRecord[“PK08”] = aPK08;

   request.Record = inRecord;

   var parameters = new MIParameters();
   var outFields : String[] = new String[1];
   outFields[0] = gCUGField4;
   parameters.OutputFields = outFields;

   request.Program = “CUSEXTMI”;
   request.Transaction = “GetFieldValue”;

   return(request);
   }

   private function CUSEXTMI_Save(aTransaction, aFile, aPK01, aPK02, aPK03, aPK04, aPK05, aPK06, aPK07, aPK08, aNum)
   {
   try
   {
   var request = new MIRequest();
   var inRecord = new MIRecord();

   inRecord[“FILE”] = aFile;
   inRecord[“PK01”] = aPK01;

   if(null != aPK02 && false == String.IsNullOrWhiteSpace(aPK02)) inRecord[“PK02”] = aPK02;
   if(null != aPK03 && false == String.IsNullOrWhiteSpace(aPK03)) inRecord[“PK03”] = aPK03;
   if(null != aPK04 && false == String.IsNullOrWhiteSpace(aPK04)) inRecord[“PK04”] = aPK04;
   if(null != aPK05 && false == String.IsNullOrWhiteSpace(aPK05)) inRecord[“PK05”] = aPK05;
   if(null != aPK06 && false == String.IsNullOrWhiteSpace(aPK06)) inRecord[“PK06”] = aPK06;
   if(null != aPK07 && false == String.IsNullOrWhiteSpace(aPK07)) inRecord[“PK07”] = aPK07;
   if(null != aPK08 && false == String.IsNullOrWhiteSpace(aPK08)) inRecord[“PK08”] = aPK08;
   //gDebug.Debug(“aNum: ” + float(aNum));
   //gDebug.Debug(“gCUGField4: ” + gCUGField4);
   //inRecord[gCUGField4] = aNum.Number;
   inRecord[gCUGField4] = float(aNum).toFixed(gControlDecimals);

   request.Record = inRecord;
   request.Program = “CUSEXTMI”;
   request.Transaction = aTransaction;

   return(request);
   }
   catch(ex)
   {
   gDebug.Error(ex);
   }
   }

   private function CUSEXTMI_ChgFieldValue(aFile, aPK01, aPK02, aPK03, aPK04, aPK05, aPK06, aPK07, aPK08, aNum)
   {
   return(CUSEXTMI_Save(“ChgFieldValue”, aFile, aPK01, aPK02, aPK03, aPK04, aPK05, aPK06, aPK07, aPK08, aNum));
   }

   private function CUSEXTMI_AddFieldValue(aFile, aPK01, aPK02, aPK03, aPK04, aPK05, aPK06, aPK07, aPK08, aNum)
   {
   return(CUSEXTMI_Save(“AddFieldValue”, aFile, aPK01, aPK02, aPK03, aPK04, aPK05, aPK06, aPK07, aPK08, aNum));
   }
   }
   }

   Reply
8. amaranto es says:

   2017/06/03 at 00:03

   And for peoples reference, you can read about CMS080 in KB: 1824822 and document ID 49129 entitled
   “M3 13.4 – Business Engine Net Change Overview – What s new in detail” I’m sorry,
   In fact I have
   My Label,40,100,51,100,1,MMITNE,SACTEST,WEITNO
   the message is :
   DEBUG: Set Controls Position
   DEBUG: +– Control:
   DEBUG: +—- Column: 40
   DEBUG: +—- Row: 1
   ERROR: TypeError: Type mismatch
   I have that letter M that appears
   Help thank

   Reply
9. aristobulonietoalcaraz says:

   2017/06/25 at 15:03

   And for peoples reference, you can read about CMS080 in KB: 1824822 and document ID 49129 entitled
   “M3 13.4 – Business Engine Net Change Overview – What s new in detail” I’m sorry,
   In fact I have
   My Label,40,100,51,100,1,MMITNE,SACTEST,WEITNO
   the message is :
   DEBUG: Set Controls Position
   DEBUG: +– Control:
   DEBUG: +—- Column: 40
   DEBUG: +—- Row: 1
   ERROR: TypeError: Type mismatch
   I have that letter M that appears
   Help thank I’m sorry,
   In fact I have
   My Label,40,100,51,100,1,MMITNE,SACTEST,WEITNO
   the message is :
   DEBUG: Set Controls Position
   DEBUG: +– Control:
   DEBUG: +—- Column: 40
   DEBUG: +—- Row: 1
   ERROR: TypeError: Type mismatch
   I have that letter M that appears
   Help thank

   Reply
10. Mike Wolfe says:

    2018/02/06 at 08:31

    I’ve been playing around with this today and have it working in the script editor and it shows on the MMS001 panel. When I am not in the script editor it does not seem to run. I have attached the script using a personalization but it does not seem to run on its own. What might I be missing? I am using 13.4.

    Mike

    Reply
    • potatoit says:

      2018/02/06 at 09:38

      Hi Mike,

      My guess is it is a naming issue.

      The name of the class needs that has the Init() method needs to be the same name as the script and the personalisation.

      So if your script is
      foobar.js

      the class needs to be foobar
      and the personalisation should be foobar (foobar.js will also work)

      Eg.

      import MForms;

      package MForms.JScript
      {
      class foobar
      {

      If you take a look at the Smart Office logs on the Smart Office client you should see it complaining that something is wrong. I also recommend changing the Smart Office clients logging to debug.

      Cheers,
      Scott

      Reply
      • Mike Wolfe says:

        2018/02/07 at 04:06

        Thanks for the quick reply Scott. I took a look at the log and this is what I see:

        2/6/2018 10:05:15 AM [Mango.Main] ERROR Mango.UI.Script.ScriptManager.LoadScript MUI0005 – Failed to compile script http://xxx.yyy.com:21107/mne/jscript/AddControl.js
        C:\Users\mwolfe\AppData\Local\Temp\1gctn0ke.0.js(157,37) : error JS1014: Invalid character

        The code does work in the jScript editor, just not in ISO.
      • potatoit says:

        2018/02/07 at 06:08

        Hi Mike,

        that’s rather odd.

        The message indicates there is an issue with line 157, I’d check it for any odd characters. Did you copy and paste some of the code from elsewhere?
        Maybe take a look in Notepad or even a hex editor to look for anything anomalous.

        Cheers,
        Scott
11. Mike Wolfe says:

    2018/02/07 at 06:45

    Scott, definitely something I could not see. RIght now ISO does not consider tab order for these fields. So I have to mouse into them to get there…same thing in H5 though.
    Thanks for all your help.
    Mike

    Reply
12. Schaerer says:

    2018/06/29 at 04:07

    Hi, thanks for this usefull script. Any idea on how to add, instead of a text box, either a date field (with calendar check) or a combo box with predefined list of values
    Thanks in advance

    Reply
    • potatoit says:

      2018/06/29 at 20:13

      The script can be used as a template to add whichever WPF controls you want – be that a ComboBox, DatePicker, CheckBox. One of the nice things about WPF is there is consistency on the field names so it shouldn’t require too much adapting.

      Reply

Leave a Reply Cancel reply

Enter your comment here...

Fill in your details below or click an icon to log in:

Email (required) (Address never made public)

Name (required)

Website

You are commenting using your WordPress.com account. ( Log Out /  Change )

You are commenting using your Facebook account. ( Log Out /  Change )

Cancel

Connecting to %s

Notify me of new comments via email.

Notify me of new posts via email.

Δ