Added a default setting in customization layer (which works) but it also locks up the field

I’ve successfully added code to a customization layer to set a checkbox to be “true” upon initialization. However, now the field is locked up and can’t be manually unchecked. This involves a called child from a parent and both have the requisite customization layer (parent dummy, child w/ changes) of the same name. The functionality is the Job Scheduling Board and the customization takes place in the “move jobs” UI panel which pops up upon moving the schedule on a job (the trigger). The field I’m setting to default of true is “Finite Capacity” and the code snippet I added is as follows:

private void edvScheduleEngine_EpiViewNotification(EpiDataView view, EpiNotifyArgs args)
{
	// ** Argument Properties and Uses **
	// view.dataView[args.Row]["FieldName"]
	// args.Row, args.Column, args.Sender, args.NotifyType
	// NotifyType.Initialize, NotifyType.AddRow, NotifyType.DeleteRow, NotifyType.InitLastView, NotifyType.InitAndResetTreeNodes
	if ((args.NotifyType == EpiTransaction.NotifyType.Initialize))
	{
		if ((args.Row > -1))
		{
			view.dataView[args.Row]["Finite"] = true;
		}
	}
}

Any insight appreciated.

@MNlesta

Try going into the Extended Properties for that field and setting Read Only to False.

It is set as “Enabled” true already and prior to the customization layer you can get into that field and un/check at will. The field isn’t greyed out so you should be able to uncheck but I can click on that field till doomsday and it doesn’t change - not even a flicker. Something about the customization layer setting a default value for the field has somehow locked it up.

A couple of things I tried:

I changed it from “notify” to “AddRow” and the checkbox doesn’t default to checked but it is open to do so.

I added in a line to set ExtendedProperties for “Enabled” to true but I get the same results - locked.

I’m very quickly exhausting whatever possible thoughts I have for tweaking the code and am more stumped than before. It’s not a complicated action and it should work so why isn’t it??? GRRRRRRRRR

For anyone interested (or who has the same problem) Epicor support was able to duplicate both in E10 AND Kinetic so it has been raised as an issue to investigate with development. Per suggestion from support I’ve raised an additional support issue with the technical team to try and get some suggestions for how to do this using a BPM against a sub-form. I wasn’t able to make it work so now we’ll see what Epicor can offer up as suggestions.

1 Like