I have a custom edit screen (single record at a time) with corresponding custom table. Similar to other edit pages, I have a primary text/search field where I want the user to enter a new value for a new record, or an existing value that selects an existing record (e.g. Stock Item or Project). The primary key of the table is an internal identity, but the UI field is a string field and unique/alternate key. Can someone remind me how to get the field to be more than a search and allow new values? I was first using a PXSelector, but I couldn’t get it to allow new values. I also then tried creating a Segmented Key with one segment for it, and then using a PXDimensionSelector and PXSegmentMask as the control, thinking it may need that to allow a new value to be entered, but that didn’t help. When attempting to save, it is not allowing a new value -- it’s showing an error that the value doesn’t exist, which of course it shouldn’t. The DAC field is shown below. What am I missing in code or UI settings, or do I need to approach it completely differently?
[PXDBString(50, IsUnicode = true, InputMask = "")]
[PXUIField(DisplayName = "Connection Name", Required = true)]
[PXDimensionSelector("SRCCONN", typeof(Search<AKTDataExtractionSource.name>),
typeof(AKTDataExtractionSource.name), SupportNewValues = true
)]
public virtual string Name { get; set; }
public abstract class name : PX.Data.BQL.BqlString.Field<name> { }
#endregion
Best answer by Tony Lanzer
View original