Can't change extended properties through customization

Epicor ERP 10
1

I built a new search button and FINALLY got that to work as desired however, when I deploy it to the PO Requisition functionality via new customization it works fine BUT there is code associated with the std search which enables 4 fields within that UI panel group. Using my new search button doesn’t automatically set those fields to enabled. If you save after search the std logic opens those fields but that is a bit clunky. Sooooooo I figure all I need to do is add a line for each field to set extended properties but alas no-go - the fields do not open up. No compile error and no change of outcome. Any ideas/help out there?? I tried to set the ReadOnly as well as the Enabled and both together but nothing changes on the UI panel. Here’s the code I’ve set up:

private void DIIbtnSupplier_Click(object sender, System.EventArgs args)
{
	// ** Place Event Handling Code Here **
	object selected = ProcessCaller.InvokeAdapterMethod(oTrans.EpiBaseForm,"QuickSearchAdapter", "ShowQuickSearchForm", new object[]
	{oTrans.EpiBaseForm, "QS_PPointActive", false, new DataTable()});
	
	if (selected != null)
	{
		string Supplier = selected.ToString().Split(';')[0];
		string PurPoint = selected.ToString().Split(';')[1];

		var edvReqDetail = ((EpiDataView)(this.oTrans.EpiDataViews["ReqDetail"]));
		if(edvReqDetail.Row >= 0)
		{
		    edvReqDetail.dataView[edvReqDetail.Row]["VendorID"] = Supplier;
		    edvReqDetail.dataView[edvReqDetail.Row]["PurPoint"] = PurPoint;
			edvReqDetail.dataView.Table.Columns["CurrencyCode"].ExtendedProperties["ReadOnly"] = false;
			edvReqDetail.dataView.Table.Columns["CurrencyCode"].ExtendedProperties["Enabled"] = true;
			edvReqDetail.dataView.Table.Columns["MfgNum"].ExtendedProperties["Enabled"] = true;
			edvReqDetail.dataView.Table.Columns["MfgPartNum"].ExtendedProperties["Enabled"] = true;
			edvReqDetail.dataView.Table.Columns["VenPartNum"].ExtendedProperties["Enabled"] = true;
			edvReqDetail.dataView.Table.Columns["DocUnitCost"].ExtendedProperties["Enabled"] = true;
			//EpiMessageBox.Show("Should fill!! " + Supplier + "  " + PurPoint);
		}
		
		//EpiMessageBox.Show("it works!! " + Supplier + "  " + PurPoint);  
	}
}

}

2

@MNlesta It is possible the Epicor has the whole dataview readonly and you can’t override that, so you will have to work around it. You can try not binding the fields and setting the fieldname to the value then assign the values to the dataview after they open up.

3

Are you saying that after loading a record into the form using the standard search these fields are enabled, but after using your custom search they don’t?

It might be possible that these controls are enabled/disabled using rowrules, and your search might not be retrieving the values required to validate those rowrules.

Part of the customization wizards is rowrules, not sure if you can see and modify base rowrules there.

4

I think you might be pushing down the right path. In later testing I noticed that when you enter a part and tab out it opens up the fields but when it’s a ad-hoc part it doesn’t but then when you enter (or click on the search) for a supplier it opens up the fields. I’m trying to update the properties to readonly false and/or enabled true in the customization layer associated with my new button but nothing happens. If you first save then that will open up the fields so I added a oTrans(Update) statement in place of the extended property changes and that works fine except it’s not flowing as “std” Epicor would and if you were thinking of backing out or killing the UI prior to completing all of the field entry thinking that it’s not saving you’d be surprised to come back in and see everything still there and the request potentially acted upon. It’s not the ideal but it is a path to solution.