Custom field in Sales Order header not showing a value

If you mean [PXUnboundDefault], you could call SetDefaultExt<GTSOOrderExt.usrShipAddressLine1> (and 2) in an event handler of FieldUpdated for Address.AddressLine1 (and 2) on your DAC fields to cause defaulting to happen any time the address fields are changed.

​@darylbowman Let me give that a try

Keep in mind you’re working with caches from several different views. If it doesn’t work, post your code.

I might be wrong, but I think fieldupdated only gets called when it is actually updated by the user.  That will work great if they change the value on the UI..  But I think the PXUnboundDefault pulls from the DB.  I will do what I can and after I fail, I will post my code.  FYI, the code I’ve posted is all the code I have so far except about 100 lines of commented out code that I tried that also failed. 

I don’t usually have much luck with this approach.  My Search2 looks valid to me.

Here is my attempt at using the PXUnboundDefault in my DAC.  

		#region UsrShipAddressLine1
		[PXString(50)]
		[PXUIField(DisplayName = "Ship Address Line 1", Enabled = false)]
		[PXDBScalar(typeof(Search2<SOShippingAddress.addressLine1, 
			InnerJoin<SOOrder, On<SOOrder.shipAddressID, Equal<SOShippingAddress.addressID>>>,
			Where<SOShippingAddress.addressID, Equal<SOOrder.shipAddressID>>>))]
		[PXUnboundDefault(typeof(Search2<SOShippingAddress.addressLine1,
			InnerJoin<SOOrder, On<SOOrder.shipAddressID, Equal<SOShippingAddress.addressID>>>,
			Where<SOShippingAddress.addressID, Equal<Current<SOOrder.shipAddressID>>>>), 
									PersistingCheck = PXPersistingCheck.Nothing)]
		public string UsrShipAddressLine1 { get; set; }
		public abstract class usrShipAddressLine1 : PX.Data.BQL.BqlString.Field<usrShipAddressLine1> { }
		#endregion

I get a runtime error:

This is the only code in my graph extension right now, but I get debug it due to the run-time error.

		protected void SOShippingAddress_AddressLine1_FieldUpdated(PXCache cache, PXFieldUpdatedEventArgs e)
		{
			var row = (SOShippingAddress)e.Row;
			if (row == null) return;

			PXCache soOrderCache = Base.Caches<SOOrder>();

			soOrderCache.SetDefaultExt<GTSOOrderExt.usrShipAddressLine1>(row);
		}

Sorry for being such a noob.

Try:

[PXUnboundDefault(typeof(Search<SOShippingAddress.addressLine1, Where<SOShippingAddress.addressID, Equal<Current<SOOrder.shipAddressID>>>>), PersistingCheck = PXPersistingCheck.Nothing)]

and remove the PXDBScalar.

If that doesn’t work, write a FieldDefaulting event handler for the field and set the logic in there instead.

I originally tried it your way and thought I was being clever by joining to the SOOrder table.  

I was SO excited… HA!

I will try doing it in a field defaulting handler now.

Here is what I tried.  No joy.  In debug, e.NewValue is being set to the address line 1. 

I can only get the FieldDefaulting to fire if I put a line in the SOOrder RowSelected.

If the next thing I try doesn’t work, I am just going to add these two fields to the SOOrder table.

protected void SOOrder_UsrShipAddressLine1_FieldDefaulting(PXCache cache, PXFieldDefaultingEventArgs e)
{
	var row = (SOOrder)e.Row; 
	if (row == null) return;

	GTSOOrderExt ext = row.GetExtension<GTSOOrderExt>();
	if (ext != null)
	{
		SOShippingAddress shipAddress = Base.Shipping_Address.Current;
		if (shipAddress != null)
		{
			e.NewValue = shipAddress.AddressLine1;
		}
	}
}

protected void SOOrder_RowSelected(PXCache cache, PXRowSelectedEventArgs e, PXRowSelected InvokeBaseHandler)
{
	if (InvokeBaseHandler != null)
		InvokeBaseHandler(cache, e);
	var row = (SOOrder)e.Row;

	if (row == null) return;

	PXUIFieldAttribute.SetEnabled<GTSOOrderExt.usrShipAddressLine1>(cache, row, false);
	PXUIFieldAttribute.SetEnabled<GTSOOrderExt.usrShipAddressLine2>(cache, row, false);

	cache.SetDefaultExt<GTSOOrderExt.usrShipAddressLine1>(row);

}

Set e.Cancel = true after setting e.NewValue

The [PXUnboundDefault] should cause the FieldDefaulting event to run during RowSelecting

​@darylbowman Daryl, thank you so much for you time on this.  

​@Django That did the trick.  Thank you for the idea.