Modifying standard entity properties and objects to “Custom” in Infor CRM

With InforCRM version 8.5.1, custom or modified items in the project explorer now show up with a specialized icon to indicate their “Custom” status.

Custom Items

Custom items

Only “Custom” items can be added to bundle manifests.  This means that any out of the box item can no longer be bundled.  Trying to drag an out-of-the-box item into a bundle manifest results in a message being presented stating that only custom items can be added to a manifest.

For items like quickforms, you could make a minor change to mark the object as a custom item, but other items may not have a property or code that you could modify slightly to do the same thing.  Fortunately, there is an easy way to make Application Architect identify an item as Custom, without having to modify that object.

For most objects, it is a simple matter of copying the xml file defining the object from the “Model” folder in the File System (LFS or VFS) to the SLXCoreCustom folder, with the same path.

Copied Items

Here,  I’ve copied the AccountDetails.main.quickform.xml from the Model folder (In an LFS) to the same location in the SLXCoreCustom folder.  I’ve also copied the Account filter.xml, GetSubTypePickListName.Method.xml and the OnBeforeInsert.method.xml

After reloading the project, then the files copied over now show up us “Custom” and can be copied over into a bundle manifest.


That can be done with pretty much any entity object.  The only exception to that is entity properties.  Entity properties are defined in the Entity’s main XML file.  For the Account entity, this would be the Account.ACCOUNT.entity.xml, that is found in the Entity’s folder under Model.

Once the Entity property you want to set as custom is found in the XML file, it is a simple matter of adding an isCustom flag to the <Property> tag and setting it to “true”.  In this example, I am adding that to the ACCOUNT and ACCOUNT_UC fields, known as AccountName and AccountNameUpper in the entity model.

Once that flag is set, entity properties now also show up as “Custom” in the Application Architect as well, and can be added to bundles.

  Pretty neat!

All the examples here are showing using a Local File System (LFS), but the same can be done using the Virtual File System (VFS) as well.


Want content like this delivered to your inbox? Sign up for our newsletter!

Jason Buss

Jason is a senior application developer with Customer FX.

Submit a Comment

Your email address will not be published. Required fields are marked *