InputMask功能异常：客户界面公司名字段仍接受非法字符

Let’s break down why your InputMask isn’t enforcing character restrictions even though the field correctly renders as a MaskEdit control:

1. Fix the InputMask Syntax #

Your current mask >AAAAAAA only restricts the first 7 characters to alphanumeric values (since A allows both letters and numbers) and converts them to uppercase. Any characters beyond those 7 won’t be restricted, which is why symbols can still be entered.

If you want to block all non-alphabetic characters across the entire 255-character field and enforce uppercase, update the InputMask to:

[PXDBString(255, IsUnicode = true, InputMask=">L{255}")]

Here’s what each part does:

• >: Converts all input characters to uppercase automatically
• L: Restricts input to only alphabetic characters (A-Z, a-z)
• {255}: Applies the L restriction to all 255 allowed characters in the field

2. Resolve the Enabled State Conflict #

Your code sets Enabled = false in the PXUIField attribute, but you mentioned you can still input values. This is a red flag:

• If the field is truly disabled, users shouldn’t be able to edit it at all. Double-check if another customization (like a screen-level override or competing DAC extension) is setting Enabled = true for this field in certain contexts.
• InputMask only works on enabled fields. If you intend users to edit this field, set Enabled = true in the PXUIField attribute.

3. Verify Customization Priority #

When using ReplaceOriginal in a customization, make sure no other customizations are overriding your InputMask setting. Check:

• Other DAC extensions targeting the BAccount.FullName field
• Screen-level ASPX customizations that might modify the control’s properties directly

4. Clear Cache and Retest #

After making changes:

1. Publish your updated customization
2. Clear the Acumatica cache (go to System > Management > Clear Cache)
3. Log out and back in to ensure the new settings take full effect

内容的提问来源于stack exchange，提问作者JB90