How to display all the digits of a Long (AKA Int64) Field in Modern UI?

Hi ​@travisk91 ,

Since this is an external key and not meant for calculations, you should store as Int64 but display as string(non db field). Using this you can display 16 digit

#region UsrExternalKeyDisplay
[PXString(20, IsUnicode = false)]
[PXUIField(DisplayName = "External Key", Enabled = false)]
[PXFormula(typeof(Selector<YourDAC.usrExternalKey, YourDAC.usrExternalKey>))]
public virtual string UsrExternalKeyDisplay
{
    get => UsrExternalKey?.ToString();
    set { }
}
public abstract class usrExternalKeyDisplay : PX.Data.BQL.BqlString.Field<usrExternalKeyDisplay> { }
#endregion

• Hide the Int64 field on the screen

• Show the string display field instead

Hope above helps!!

Ah, yes, that’s super helpful!

Is there a good workaround for the rare occasion that I need to populate that value from the UI?

Sometimes a value will get out of sync and need attention. Is there a proper method for editing a really big long int?

Hi ​@travisk91 ,

For the rare case where you need to edit the value from the UI, the cleanest approach is to make the string display field editable and write the parsed value back to the underlying Int64 field via the setter:
#region UsrExternalKeyDisplay
[PXString(20, IsUnicode = false)]
[PXUIField(DisplayName = "External Key")]
public virtual string UsrExternalKeyDisplay
{
    get => UsrExternalKey?.ToString();
    set
    {
        if (long.TryParse(value, out long parsed))
            UsrExternalKey = parsed;
    }
}
public abstract class usrExternalKeyDisplay : PX.Data.BQL.BqlString.Field<usrExternalKeyDisplay> { }
#endregion

This way the user types the 16-digit value as a string, and the setter validates and converts it back to Int64 before saving. The actual DB field (UsrExternalKey) remains Int64 — nothing changes in your data model.
A couple of things to keep in mind:

Remove the Enabled = false from PXUIField so the field becomes editable.
Optionally add a PXUIVerify or validation in FieldVerifying to reject non-numeric input and give the user a clean error message.
You can also remove the PXFormula attribute from Rakshanda’s example if needed, since the getter/setter handles the sync directly.

Hope that covers it!