Custom Fields Configuration

OVERVIEW

️ This guide provides instructions on how to display Custom Fields in the Epicor Kinetic Warehouse (EKW) application from Epicor.

EMW (Epicor Mobile Warehouse)

  • refers to the previous name of EKW (Epicor Kinetic Warehouse).

PREREQUISITES

Before proceeding with this this guide, the following conditions should be accounted for:

  • The user is using release 3.0.0 or greater of EKW.

  • The user has a basic knowledge of creating UD columns in Epicor.

  1. Creating custom fields using custom UD field methodology: Refer to this Guide: https://biscit.atlassian.net/l/cp/mXF8wJeK

  2. Creating custom fields using the BPM form: Refer to the following Video: https://youtu.be/1oVqF9aM1Us?si=w3Y-ApiqM8cZAWJN

IMPLEMENTATION

In order to have the Custom Fields appear in the EKW application, the user must first set up UD columns. For the custom fields to appear correctly in EKW, the following requirements must be met:

  • Four UD columns must be created to indicate: the column to be displayed, the label, the type and if it should be disabled.

  • The UD columns should be formatted like the following (col1 increments for each new custom field – do not miss a number as it will not display the following fields):

  1. Emw_col1_column_c – the initial value should be set to the column that it references on the dataset.

  2. Emw_col1_label_c – the initial value should be set to the label to be displayed in EKW.

  1. Emw_col1_type_c – the initial value should be set to the type of the data.

  2. The available options are text, description, number, Boolean, list.

Available Field Types:

  • Number Will display a number input box in forms.

  • Text Will display a text input box in forms.

  • Description Will display a text area input box in forms.

  • Boolean Will display as a checkbox in forms.

  • List Will display as text in lists and will NOT be displayed in forms.

  • A Boolean type will display as a checked or unchecked box, depending on the value.

  1. Emw_col1_disabled_c – the initial value should be set to whether or not the value can be changed or not.

  2. This column has a data type of Boolean:

If there are multiple custom fields on a dataset, the User Defined Column Maintenance form will appear like the following:

Once all the UD columns are created, the user will need to Regenerate the Data Model and recycle the application pool. There is a disabled property where if needs to the customers create BPMs and alter the dataset being returned to EKW to say that the field needs to be disabled.

️ While the custom fields can be used extensively throughout the EKW application they are unable to be used in some instance. These instances include:

  • Datasets that do not have a table in the database. For example, the dataset Inv Trans does not have a table in Epicor and therefore a UD column is unable to be added to it.

  • Datasets that come through on a Get List call do not return UD columns. For example, the CCHdr is returned on a Get List call which does not return UD Columns.

PDF file with examples:

3MB
EKW Custom Fields configuration 1.pdf
pdf
PreviousLanguage PacksNextUser Guide

Last updated

Was this helpful?