Posts

Control Properties in MEC

Image
When we want to keep some parameters in the MEC we often use “.properties” file.  But alternatively we also can use Control properties in the Partner Administrator.
The control properties can be accessed from the MEC mapper using the following code.
String strVariable = getManifestInfo("agr:outputFolderPath");
Hint: You can add control properties to the individual “Agreement” or to the “Group”.
Depending on the situation, we can choose the suitable method to use. Below comparison will help to choose appropriate method.
Comparison:
Control PropertiesProperties FileFormatKey,Value formatKey, Value formatDeploymentWill be ported to the environment with import/export function.Possibility to miss the file to copy unless it is documented properly. CodeVery easy. No explicit initiation of objects.One line required to access the variable.  Not very easy. Need to read the file and initiate property object. Require few extra coding to access first variable.UsageProperties to be used in a…

Infor M3 TechEd 2017

Image
It is so exciting to be here in Sweden & to participate 2nd Infor M3 TechEd event. In the keynote session today (by Ole Ramsussen – Infor M3 Product Global Director) following key points were mentioned. Infor Xi platform   There are 3 extensibility levels for end users (HomePages), consultants(App Builder) & developers(Mongoose).13.4 highlights Full support of Xi platformAvailable both on-prem & cloudExtensibility improvements 288 performance improvementsFactory Track as warehouse mobility solutionSoho designCloud strategy  Multi tenant ColudSuites 11.1 M3 CE planned to release in 2018 for F&B , Distribution enterprise, Fashion, Equipment & chemicals M3 Cloud Edition 19.1 panned to release in 2019.Infor M3 roadmap Utilize the power of Xi platformRemove tech legacy Cloud strategy as above point #3Strategically below components are going away.IPA –> ION WorkflowLBI –> InforBI/BirstISO –> M3 H5 client/MingleMashup Designer –> Infor App Builder Infor OS : I…

Access APIs , When you don’t have MI Test

Image
When you want to run an API, MITest (external tool or inside ISO Client ) is a handy tool. But if you have them, for an example in H5 client you cannot call MITEST, still, there is a way to an API. You need to have LCM access or server view access.
Steps: Following steps were captured in LCM.Go to the Topology View in Infor ION Grid Management pages and find M3ApiWS.  The expand it.
Then Click on MI-WS. Then click on Global Management Pages (M3-API-WS). In the next
You will get the page where you can select Program, Transaction & run.

A New Beginning

Image
Today we embarked a new journey. Brandix I3 became Fortude (http://fortude.co/) . I’m very proud that I WAS one of the first team at Brandix I3 & I’M now one of the first team at Fortude. My Team & I, as M3 development team,  supported to grow Brandix I3, working with almost  all it’s customers. We are not going to stop. We are endeavouring as development HUB to grow Fortude exponentially. !

Browse Control for ISO SDK App–Part 1

Image
BackgroundIn a conventional M3 Program, data in some fields can be searched by pressing the F4 key or Browse function. Using MAK (M3 Adaptation Kit – the framework to develop M3 programs), it is just mater of overriding  PxPMT() to enable this Browse feature. However, in SDK development, we don’t have that option. Neither a function to override nor control to re-use.  Instead, using WPF & C# we have to create it from the scratch. I did this for my current SDK project and going to share with SDK development community. There is an article in Potato IT blog (https://potatoit.kiwi/2013/09/19/smart-office-sdk-first-project-part-6-the-browse-control/).  This was a good starting point for me. However, since I have MAK background, I wanted to implement similar way, that PxPMT() method does (below is an excerpt of  M3 Browse )if(IN62){if(DSP.hasFocus("W1TOOL")){this.PXFILE.moveLeft("CSYTAB00");this.PXMBR.clear();this.PXOPT='1';this.PXKVA1.moveLeft(LDAZD.CONO,3);…

Read Profile Settings from ISO SDK App

Image
BackgroundAccessing  Web Services, external data sources from a SDK app is common like other technologies do. To store these access points, parameters etc. can be done in various ways. In a .net application common scenario is store then in the .config file or setting file. Why we want to do like this is, avoid hassles of deployment. When ISO SDK application is considered, we can achieve same thing by using .manifest file.ProblemI need to get database connection string from the M3 profile.Solution Using Profile Editor, add a setting to store database connection string. For this example, I’m going to use setting name as “DbConnection”.
Use the following code to extract above information.
txtDBConStr.Text= ApplicationServices.SystemProfile.GetProperty("M3", "SDKApp", "DbConnection");

MEC: How to Set Message Counter for EDI Message

Image
When you sending/creating EDI messages it is necessary to include unique message interchange number. This is to ensure each message that we are sending is unique. In EANCOM/EDIFACTElement 0020 of UNB segment:
UNB+UNOA:4+xxxxxxx:14+xxxxxx+20160905:0831+00000000000057+    +ORDERS++1'In X12Element ISA13 of ISA segment:
ISA*00* *00* *ZZ*167520391 *ZZ*39319445 *991201*1248*U*00200*000000001*0*P*>This number need to be persistent. The middleware we are using for EDI transformation should cater this requirement. I used MS-BizTalk  Server for two EDI projects, which cater the same. (just by a configuration)M3 e-Collaborator (MEC) does the same thing in a different way. In the MEC database (e.g. MEC_Storage_TST) has a table (UTIL_Message_Counters) for this purpose. Table structure is like this:Note 1: To be able to use this class you must first create this table (use the SQL script MeC_Utilities_db_script.sql). You don’t have to enter a record or write code to save/get data. Instead, you …