Add a Profile fragment with Smart Office SDK

Continuing my previous and previous posts on Infor Smart Office SDK, I will now post on how to add a profile fragment in Smart Office Developer mode. For that, I will follow the instructions from the Developer’s Guide and from Karin’s comments.

We use the <Profile> section of the feature Manifest to merge our settings into the system profile. It gets merged only when the feature is deployed to the server with LifeCycle Manager (LCM). It doesn’t get merged when Smart Office is running in Developer mode. The workaround is to use a local profile.xml and reference it in our Windows Registry. First we need to get the server’s profile.xml.

Find the server’s profile.xml

In old versions of Smart Office, the file profile.xml used to be an actual file on the server. Now with the Infor Grid the file has been moved into a distributed database. Supposing you have such version of Smart Office:

  1. Go to your H2 Web Console following Scott’s instructions, login to the MangoServer application, click on the CATEGORYFILES table, it will display the contents of the table, and copy the CONTENT of profile.xml:
  2. HEX-decode the contents, for example with Notepad++ or Ostermiller’s decoder:
  3. Save the decoded contents to a file profile.xml somewhere on your computer, and ensure it’s valid XML:
  4. That’s the server’s profile.xml.

Add your fragment

Now you can add your settings:

  1. Open the file profile.xml with a text editor like Notepad, add your application group (or extend an existing one), and add your settings, for example:
    <applicationgroup name="Thibaud">
            <A1>Hello World!</A1>
            <B2>["abc", "def"]</B2>
            <B3>{ "msg": "I'm a value!" }</B3>
  2. Ensure the file is still valid XML:
  3. Optionally, you can add Description attributes at each element, and enabled=”true” on the applicationgroup.

Reference the file in Windows Registry

Now tell Smart Office Developer mode to use that profile.xml:

  1. Start your Windows Registry Editor (C:\Windows\regedit.exe).
  2. Go to the Smart Office SDK Window Registry Key HKEY_CURRENT_USER\Software\Infor\MangoDev
  3. Add a String value ProfilePath, and set the value to the path of your profile.xml:

Test in Smart Office

Now test it in Smart Office Developer mode:

  1. Now re-start Smart Office in Developer mode (from your Visual Studio solution).
  2. Start the Profile Editor from the Navigator widget > Administration tools.
  3. Select your application group, Thibaud in my example.
  4. Select Advanced and your settings are there:

That’s it!

If you liked this, click the Follow link below to subscribe to this blog. And join the authors and share your own M3 ideas with us.

Related articles


Published by


ex- M3 Technical Consultant

4 thoughts on “Add a Profile fragment with Smart Office SDK”

  1. UPDATE: You can also get the file profile.xml by calling the SOAP Web Service at http://theserver:theport/mangows/MangoProfileManager?wsdl . In SOAP UI, use the HTTP scheme (non-secure) and respective port number on the WSDL URL to create a new SOAP Project, and use the HTTPS scheme (secure) and respective port number on the endpoint to execute the web service. For input values, set the <get:GetProfilesRequest> to the string dummy. In the Auth tab at the bottom of SoapUI, set your Smart Office username/password. Click Submit to execute. The SOAP Response Body will contain a CDATA section with the profile.xml. Unfortunately you cannot use the Web service test tool of Smart Office (tool://wstest) because the returned value is XML in CDATA and it won’t show in the Output tab of the test tool.


  2. I just wanted to thank you for all your ideas and information on M3. We are in the process of installing a new system and it has been a major help in getting things done. You and your efforts are very much appreciated here


    1. Hi Steve. Thank you for the feedback. I appreciate when I hear back from the community, and when I meet new people. Can you share more about your process of installing a new system?


Leave a Reply

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

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

Twitter picture

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

Facebook photo

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

Connecting to %s