We are beginning the process of re-writing our classic customisations to function within Kinetic. We have encountered difficulties in making UD fields available in the Kinetic interface. Our OrderDtl table has been extended to include a UD field called Location_c. This immediately becomes available to view in the Classic Order Entry screen…
Accessing the Kinetic Screen, the new field is not available.
Personalising the grid allows me to display the column.
Unless I am mistaken this does not appear to be a scalable solution, it will be difficult for us to personalise the screens of 100 users.
I am probably missing a step as I cannot believe that Kinetic doesn’t provide a solution to what is a base requirement. Does anyone have a guide on how to achieve this mod?
UD Columns should be available in the Dataview in Kinetic, just as they were/are in Classic. The fact that you CAN add it as a personalization means that it IS available.
If you want it to be visible by default in the particular grid, you’ll need to add it to the grid via customization layer. Then it will be visible to all users, by default, without the need for individual personalizations.
Thank you for the kind welcome. Whilst I have a customisation layer created the grid does not appear to have any function that allows me to add or hide columns.
So, since your image above was PO Entry… I’ll show that…
Open up your custom layer in App Studio. Navigate to the page with the grid you’re trying to work with. Click on the grid (to highlight it) and click on properties over on the right side of the screen.
Expand “Data”… then click on “Grid Model”.
Scroll down and you should see another area called “Columns”… open that.
In the “Columns” area, you’ll see a dropdown which should contain all the columns that are currently viewable in the grid:
You’ll want to click the (+) icon to add a new column. You’ll type the Field Name and give it a “Title” (the column heading as you want it to appear).
That’s really all you need to do. Preview the layer and see if it now appears in the grid. If so, you can save & publish your layer. If you haven’t previously applied this custom layer to your menu… you’ll have to do that in Menu Maintenance.
The downside is, it is going to add the 'new" column to the end of the grid. If that’s cool… good, you’re done. If NOT… there’s no CLEAR way to re-arrange the grid column order. Some have found success in clicking/dragging the fields around in Application Studio… and again, saving. Hopefully that will work for you:
Thank you for your help. I have attempted to make the modifications as specified without success. The only way possible to view the data is by using the Personalize Columns feature to un-hide the column.
I cannot believe that Epicor does not support a basic feature such as the ability to pre-determine column positioning.
No he’s right, it actually isn’t possible in some screens, where the dataview is coming from service that doesn’t automatically contain UD columns from the header table you would assume is the data source. That’s the problem that lead me to create the idea about making it easy to add columns to a landing page. Its really frustrating if its not already in the data view. That said I am still not sure which screen is actually being discussed here, or which grid.
Landing pages… that may be true. I originally thought the image from the OP showed the PO Line Details grid on the PO Header form (because I saw the PO field)… but I was mistaken on that. That’s the field for the customer’s PO number.
I think my example of the Sales Order Line Detail grid on the Sales Order form was correct… I think.
Location_c SHOULD be included in the OrderDtl dataview… just like my UD columns were included in mine.
The UD Field Location_c did exist in the dataview. I tracked the issue down to the fact that I was populating the EpBinding data input with the Table and Column name, in this case OrderDtl.Location_c. Clearing this value resolved the issue.
