Global field to create for data entry

[JMart]

My apologies if i am posting in the wrong group.

I just want to get feed back on how other are doing data entry particularly when creating a new record.

Normally when i create a new record I like using global field for the key data (I consider key field those field required when creating a record).

Then i use a save button, that with a script that created the new record with the required initial data information. 

Is this a good practice?

Thanks

JMart

[Steve Martino]

I’ve used that technique.  If it does what you need it to do, then it’s fine, right?  
There’s just the overhead of the global fields, and usually a script to initialize and eventually clear those fields.

But you can also just do New Record, and prevent committing the record unless they hit a 'Save' button, or something similar and use the 'Save' script to validate your data before committing the record, or a 'Cancel'  button to revert (not commit).

[Fitch]

I wrote an article last year showing how to do what Steve's talking about:

https://www.fitchandfitch.com/2020/05/modern-commitment/

(My site has an expired SSL certificate right now, so you may get an ominous security warning, but I assure you it's perfectly safe.)

I agree with Steve, no reason to change your globals. But if I'm creating something new I'll most likely use the script trigger method.

[bcooney]

We dedicate a utility table of globals by entity. So, rather than one massive table of globals, we have several utility tables. Often, the new record actually involves creating several records, and so the utility tables values are packaged up in a json object and sent to a transactional “api” script. The api will set default values and enforce business rules, such as required values.