App Studio - Grid Column Addition Issues

Kinetic ERP
,
1

I am attempting to add the JobMtl.TotalCost column to the Materials Landing Grid in Job Tracker and experiencing weird results.

I am displaying this column in the Classic UI as shown below.

Classic
Classic723×545 112 KB

I was hoping TotalCost would just be hidden in Personalization in the Kinetic UI, but it wasn’t listed. I created a new Layer, found the Materials Landing Page, Edit, highlighted the grid, went to Data > Grid Model > Columns and added the TotalCost column as described in the Epicor Learning Center Course ‘My First Layer in Application Studio’ with properties entered as shown below.

Props_PerCourse
Props_PerCourse398×523 19.3 KB

When I preview the layer, my Total Cost column does not appear.
PreviewMissing

The only way I can get the column to appear is to change the Field property to be JobMtl.TotalCost
Prop_Appears
PreviewPresent

As you can see from the screen shot above, the field is blank to the particular Job I entered in Job Tracker. I checked the JobMtl table for the Job and there should be an amount displayed. I have tried varying combinations in Properties for this field and it does not populate.

I checked under DataViews for JobMtl and the field is listed under Columns, so I’m assuming I don’t need to create a dataview and event to have this field populate?

dataview
dataview1652×858 180 KB

This is only the 5th Customization I’ve recreated in App Studio so I’m still learning, but I feel like this should be easy; what did I miss?

Thanks in advance.

2

I think your logic and set-up are good. I just tried to recreate it and also could not get it to display. Perhaps should report it as a bug?

1 Like
3

I thought the setup was okay, but it didn’t make sense that following the course would not allow the column to appear, but adding the table name allowed it to appear.

My next stop was support, but I wanted to check in here first since this is all so new. Thanks for checking and confirming it didn’t work for you as well.

4

Quick update for those interested.

I opened a support ticket on this issue and they were able to reproduce the issue in 2023.2.14 (I am on 2023.2.11). They are going to write a PRB and submit it to development.

1 Like