Add JobComplete field to Project WBS Phase List

[jadixon (Jeanne)]

I’m sure there are answers out there but I am having trouble finding what I think is the right one.

I want to add the JobComplete flag to the Project WBS Phase list on the Project entry form. I see that the grid is bound to ProjPhase but it also has the Job Release there which is not stored in the ProjPhase table, so there must be something somewhere that pulls the phase job data in. I want to be able to update it as well as view it.

What is the proper way to add that to the grid?

[jbooker (Josh Booker)]

Not sure about editing the field but think this is still the most recent and recommended (among users) way to add grid columns. @klincecum ?

Showing UD Field values from JobHead in Job Entry LandingPage View

READ THIS FIRST —> @hmwillett linked to this as the potential new recommended way to add custom fields to grids. While this post does have most of the information, it may not be the best example of what to do, especially if you don’t know what you are doing. I will make a new thread soon with the basics in a safe way. <— READ THIS FIRST Ok, here is how I did it. For the first part, here is what I did. I don’t think you actually need to do this part, since you said your layer was…

[klincecum (Kevin Lincecum)]

I need to update that with some safer practices.

[jadixon (Jeanne)]

I’ll keep this in mind for the future, but we are still on Epicor 10 at the moment (we are trying to get to Kinetic right now).

The issue isn’t adding a UD field, it is adding a field from the JobHead table into the existing ProjPhase query on the project entry form. Not sure if that makes a difference. One thought I just had would be to hide the base grid and create my own from an updateable BAQ, but I am not sure if that is the best approach.

[jbooker (Josh Booker)]

So my limited understanding is there are significant issues with replacing the existing grids on system apps. Not the least of which is you must recreate all the rules and events on the grid.

So instead of replacing, one way is to create a dummy field in the phases dataset and set that field by iterating over the JobHead table. This technique was shown on here by @hmwillett. you add a dataset with JobHead to the app then add a dummy field to the existing grid and then iterate over JobHead to find the related record and set the dummy field.

This method was difficult but works. I added InvoicePaid to Project Milestones this way. Later on, @klincecum shared his approach which basically adds related fields from other tables to the phases dataset. No replacing built-in grid, no iteration.

So adding related data to existing grid isn’t easily done but Kevin’s is the best method to my understanding.

Hope that helps.