BPM or Function or Application Studio Event?

A bit of background information first, we do not have access to the custom code widgets; otherwise, this would have been solved in 5 minutes. Next, this is not a permanent solution. We are working with TSG to create a massive customization for after go-live to streamline the process.

I am looking to uncheck the production yield box in the child jobs when we batch them. I have dug into methods, data directives, and application studio events. I cannot seem to figure it out without the custom code widgets.

I have tried to do a data directive on JobHead for a condition that ties the temp table to job prod and only filters on jobs that match the targetjobnum.

I have tried to do a data directive on job prod and did a table update based on the records filtered on jobhead that have matched the targetjobnumber.

I tried to insert an event for after createbatch that updates the data set for _Selectedjobs.ProductionYield. If I am being honest, this is the only one that I am not sure about. Based on what I can tell, that isn’t a part of that DS, but I cannot find where to modify that DS either.

Let me know what additional information I can provide. I am sure I am not the first person to do this, but I am sure I am the first person (maybe second) to try to do it without the custom code widget.

1 Like

Why?

1 Like

We didnt pay for some SDK license or something like that.

It’s part of the base product. I doubt your permissions are correct.

1 Like

It is not part of the base for cloud customers (to my knowledge)

You don’t need the sdk to use the custom code widget.

1 Like

I have spoke to a Epicor consultant (that we have onsite) and she said in order to use those widgets we would have to purchase that license.

I’m pretty sure you are both confused, or not explaining it right.

Why don’t you start over.

1 Like

Check your user permissions for BPM Advanced User.

3 Likes

…
…
…
So yea I am very new to cloud environment and just accepted this as how it was in the cloud. To be fair on my security manager account I do have that option checked. But there seems to be a bug with having automation studio and BPMs. Once we add automation studio access to a user it gets errors when trying to access BPMs.

Well Im off to go custom code. Thank you for giving me my baby back!

1 Like

And if you’re trying to do this from Kinetic screens, you should be in the groups “Method Directives for Kinetic” and “Data Directives for Kinetic”.

Brother I am so upset… I have been banging my head against the wall for the last two days and this should have been done within 10 minutes…

4 Likes

Welcome to the club.

:people_hugging:

1 Like

May want to look for a new consultant as well…

4 Likes

To be fair, we checked all the boxes on my admin account, but again, there have been recent issues with accessing BPMs since 2025.1.11.

We both assumed I had every check box checked, and then I was told Oh, that is probably for the SDK license. She is also an OPs consultant, not a customization or TSG consultant.

Other than that slip of the tongue, she has been amazing!

2 Likes

My code is a hot mess. First round on me at the next insights…

var ttRow = ds.JobHead.FirstOrDefault();
var ttRow2 = ds.JobProd.FirstOrDefault();
if(ttRow != null)
{
  string jobNum = ttRow.JobNum;
  var jobSvc = Ice.Assemblies.ServiceRenderer.GetService<JobEntrySvcContract>(Db);
  var jobDS = jobSvc.GetByID(ttRow.JobNum);
  
  bool ProdYield = ttRow.ProductionYield;
  string TargetJobNum = ttRow2.TargetJobNum;

  if (ProdYield = true)
  {
    if (TargetJobNum !=  string.Empty)
    {
        ttRow.JobNum = ttRow2.TargetJobNum;
        ttRow.ProductionYield = false; 

        jobSvc.Update(ref jobDS);
    }

  }
  
}

Or it could be the method I am trying to run it off of. I am trying to run it off of the JobEntry.Update.

1 Like

You just assigned that to true… Use ==

1 Like

That did not work, I wonder if I should be doing this as a function and calling that function after an event on the resource scheduling board.

I didn’t look at the rest of the code, or what you are doing.

Just pointing out the obvious error.

1 Like

I might close this post down and then start a new one with the current code issues.

3 Likes