I am trying to create an update-able BAQ so that i can update the resource groups and resources for each operation on all of my companies jobs. I have watched a good amount of youtube videos on how to make an update-able BAQ but i still cannot get the baq to save.
i have simplified it down to using JUST JobOperDtl to pull in the Company, JobNum, OprSeq, ResourceGrpID, and ResourceID fields.
I set the BAQ to Update-able, went to the update tab, set which fields i want to update, and then search for the business object, the only one im presented with is Erp.JobEntry⌠After selecting that ill try and test it but im faced with the following errors:
Problems in BAQ update processing
Expression for JobOpDtl.AssemblySeq contains non-existent result column
Expression for JobOpDtl.OpDtlSeq contains non-existent result column
Expression for JobOper.JobNum contains non-existent result column
Expression for JobOper.AssemblySeq contains non-existent result column
Expression for JobOper.OprSeq contains non-existent result column
Expression for JobAsmbl.JobNum contains non-existent result column
Expression for JobAsmbl.AssemblySeq contains non-existent result column
Expression for JobHead.JobNum contains non-existent result column
Unable to save updatable BAQ
See âProblems in BAQ update processingâ section for details.
Uncheck updatable flag on general tab to save updatable BAQ.
i donât understand what its telling me or why its telling me JobHead is causing an issue when i donât have that field in this BAQ. Can someone help clarify what mistake i am making?
It needs to have a minimum amount of fields in the query to identify the row. Add those rows to your BAQ fields, then reslect the method. The errors are telling you that it doesnât have enough identifying information to know the specific row to modify.
Thanks for the guidance but that causes another problem unless im not understanding you correctly. if i add those fields under display fields, i now have a ton of duplicate fields that i never wanted. why would it tell me to have Company for OpDtl, Oper, and JobAssembly?
It worked by the way! although its full of duplicates, i was able to run it so thank you for your help there.
those fields are needed to know which things you are updating. If I told you add paint to that part, you would say âwhich part?â I would have to specify the job, and the part number, and then add the operation. The resources are under the operation so you need all of the identifying information all of the way up to job head (resource , resource group , operation sequence, asm seq, job num) or the system says âwhich one?â If you donât want those to be update able, you can uncheck the update able check box and they wonât show up in the pop-up when you double click the row, but they still need to be shown in the query.
As far as having extra fields in the query, Epicor is assuming that an individual that is using the query screen is savvy enough to understand which fields to pay attention to. If you want to clean that up more, you can import that into a Udashboard and only show the requisite fields. Since the query still has the underlying identifying information, it knows which thing to update. But if you donât shows those things, to the user, it will look like the rows are duplicates because you canât see what is different.
Also, I think that you might have a misunderstanding of how the job tables work. When you get details on a job, it goes to all of the appropriate tables (partmtl, partop, whatever the resource group stuff is) and aggregates that into a line for each part on the job. Now they are disconnected from the master and you can manipulate things specific to the job. If they looked up the master information every time, you would affect other jobs, and that may not be desired. (for example if you are making a change and it needs to be the old way until certain jobs are through the shop). Thatâs why there are so many more rows on the job stuff, but fewer tables. Not the best explanation, but something one needs to understand to manage jobs effectively.
If you have a related field already in there from a different table, you can simply copy the expression from one table to the other:
ie Expression for JobHead.JobNum can be set to ttResult.JobOpDtl_JobNum
And that way you have no additional/repeated columns. Like Brandon mentioned though, it is best to display those fields in the uBAQ and simply hide them when creating your uDashboard assembly.
If you scroll down, you should see those rows with nothing in the Expression field. Copy the info in the related field from the other table. Note, you need to have a related field displayed on the query to be able to copy the ttResult expression, so youâll need to add JobOpDtl.AssemblySeq to your query at the very least.
So after working with Epicor support, their agent Juan helped me get a working Ubaq and dashboard.
for anyone who finds themselves here looking for a solution i needed to have my baq setup a little differently than i first laid it out (see first picture for proper layout). I also needed to have multi-row update turned on.
