http://peoplesofttipster.com/2007/05/22/state-records-and-missing-data/ A PeopleSoft Tips and Tricks Blog Wed, 14 Dec 2011 14:35:44 +0000 hourly 1 http://wordpress.com/ http://peoplesofttipster.com/2007/05/22/state-records-and-missing-data/#comment-129 Tue, 03 Jul 2007 22:30:32 +0000 http://peoplesofttipster.com/2007/05/22/state-records-and-missing-data/#comment-129 I certainly develop most of my AEs with the State Record as a SQL Table, partly as it aids with debugging. It’s a surprise how many people disagree with this approach though. I concede that having the AETs as a Dynamic/Work records avoids the overhead of the data being saved to the DB at each commit, but honestly can’t see that saving a single row of data (after all that’s all an AET will contain) presents a significant overhead.

]]> http://peoplesofttipster.com/2007/05/22/state-records-and-missing-data/#comment-123 Mon, 02 Jul 2007 13:24:40 +0000 http://peoplesofttipster.com/2007/05/22/state-records-and-missing-data/#comment-123 I build all my AET’s as SQL tables. I don’t believe there is any downside to this approach. My AppEngine instructor recommended avoiding derived/work state records. What are you hoping to gain by setting your table type to derived/work?

]]>