News and Announcements icon

Dynamics 365 CommunityForums Microsoft Dynamics SL (Archived) Custom tables best pra...

Microsoft Dynamics SL (Archived)

Custom tables best practices

(0) Share

Report

Report

Posted on by Mary Letourneau

100

I've noticed that all the standard tables in Solomon contain the following six fields that help with tracking who's modified tables:

Crtd_DateTime, Crtd_Program, Crtd_User - List the user, program and date-time the row was first created;

LUpd_DateTime, LUpd_Program, LUpd_User - List the user, program and date-time that the row was last modified.

Are these fields something I should be implementing in new tables that I add to the system?

If so, am I correct in assuming that I would be writing my own UpdateEvent code. Any best practices I should be aware of?

*This post is locked for comments

All responses Img

All responses (1)

Answers Img

Answers (1)

Verified answer

Barry Flynn 3,090 on at

Like (0)

Report

Re: Custom tables best practices

Mary

It is not compulsory to have those fields, but it can be useful, and I think it should usually br done.

Yes you do need to write your own code to populate those fields.

For grids, this will probably be in the LineChk event.

Otherwise the Update event.

In both cases, you need to check whether this is an Insert or an Update, then update the LUpd fields and/or the Crtd fields as appropriate .

Barry

Helpful resources

Quick Links

Leaderboard

#1

André Arnaud de Cal... 291,269 Super User 2024 Season 2

#2

Martin Dráb 230,198 Most Valuable Professional

#3

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans