Hi @darylbowman,

From my testing in 22R209 using Sales Order and Shipments screens, I wasn’t able to reproduce the issue. I was able to create a Custom field UsrNotes and was able to save/retrieve the values without any issues.

Can you please share more details like, steps to reproduce, is the issue specific to screens, or share a customization package using which we could reproduce the issue? 

Thanks,

Hey @Vignesh Ponnusamy,

The table was entirely custom, therefore the column name was ‘Notes’, not ‘UsrNotes’.

Here’s the field definition:

#region Notes
NPXDBString(2000, IsUnicode = true, InputMask = "")]
 PXUIField(DisplayName = "Notes")]
public virtual string Notes { get; set; }
public abstract class notes : PX.Data.BQL.BqlString.Field<notes> { }
#endregion

I'm now a little confused because in the same package were other custom tables with 'Notes' columns that have no issues, but for whatever reason, renaming the column to 'Note' fixed it and changing it back to 'Notes' broke it once more.

I did some research and discovered that the word Notes is reserved and used in parts of the web UI controls.
Look at the screenshot below:

The "string field defaulting to zero (0)" text makes me think that this is due to PXGridRow

By the way, looks like the word "Files" is also reserved.

Thanks @vardan22 

I wouldn't have thought to look there, but that makes sense.