@creece I ended up forcing the field to 13 characters so the dashes don’t fit, but then I created a second field that sources the first one but uses

SUBSTR()

to add the dashes where they need to be. Then did a workflow to show and hide the respective fields on view/edit. It looks like to the end user they just put in the numbers and when they save it the dashes are automatically added.