New field request: {Contact.USPTORegNumComma}

[SadiqA2304]

{Contact.USPTORegNumComma}

• Returns Contact's registration number with a comma where appropriate

Example 1:
{Contact.USPTORegNum} = 11222
{Contact.USPTORegNumComma} = 11,222

Example 2:
{Contact.USPTORegNum} = 100000
{Contact.USPTORegNumComma} = 100,000

[SadiqA2304]

@RichardS3059 I like the idea - but I'm not optimistic that Appcoll will add new syntax when it would be easier for them to add a new field. On the user side of things, learning syntax is a similar amount of effort as looking up/remembering field names is similar effort, if not more effort imo.

[RichardS3059]

@SadiqA2304 The format I proposed is very similar to the way you can format cells in Excel and the way date fields can already be formatted, But the real advantage would be that you wouldn't be limited to specific fields, but could format any field you want however you like it.

[SadiqA2304]

@RichardS3059 OK... so instead of having to remember a "new" field name, you have to remember to type in your proposed new syntax for the "old" field name? I don't see how your proposal makes things easier... in fact seems a bit more complicated. As far as "remembering" field names, I think that's a non-issue - the documentation is available and all fields are provided there. Personally I haven't memorized any field names despite using fields and forms heavily.

[RichardS3059]

@SadiqA2304 Instead of a new field, I'd rather have AppColl allow formatting characteristics in non-date fields like it does with dates. Something like:

{Contact.USPTORegNum(#dd,ddd)}

That way I don't have to remember yet another field name.