• Search Forums
    Advanced Search Topics Posts
Prev
Next
Forums User Experience Lawson Add-Ins for Microsoft Office

Addins is too quick...

 3 Replies
 0 Subscribed to this topic
 1 Subscribed to this forum
Sort:
Author
Messages
BrianP
Advanced Member
Posts: 35
Advanced Member
Helpful Replier
New Poster
Engaged Poster
Engaged Reader
Avid Reader
7/8/2009 5:29 PM
I know it is hard to believe (and i can't believe i am asking) but, I need to slow down the Addins upload to one entry per second.  The reason behind it... APAUDIT has a time field (APA-TRANS-TIME) that is updated during a delete load I am working on in AP10.6 and the process aborts with a duplicate record error due to the time (HHMMSS).  So far I have been able to insert several lines of old data between the rows that could cause a failure and it appears to be working fine, however, with a single load file of tens of thousands records this method may not be the most effecient.  Any thoughts?
John Henley
Posts: 3362
Helpful Replier
New Poster
Engaged Poster
Avid Poster
Engaged Reader
Avid Reader
7/9/2009 1:23 PM
This is yet another great example of where Lawson just isn't "enterprise-ready".  To have an index based on date/time, and not to have two records able to have the same timestamp is just ridiculous.

What apps version are you on? I have seem some patches to fix this...
Thanks for using the LawsonGuru.com forums!
John
BrianP
Advanced Member
Posts: 35
Advanced Member
Helpful Replier
New Poster
Engaged Poster
Engaged Reader
Avid Reader
7/13/2009 8:16 PM
Thanks for the response John! We are upgrading from v8.0.3 to v9.0.0.5 (go-live is Feb. 2010), I see the same logic in both versions.
Norm
Veteran Member
Posts: 40
Veteran Member
Helpful Replier
Engaged Reader
Avid Reader
7/20/2009 5:03 PM
My condolences Brian. I vaguely remembering somebody having a problem like that, but not during a conversion where thousands of records needed to be updated.

A quick calculation says that 10,000 updates @ 1 second per update = over 2 hours 45 minutes per 10K records. That seems awfully slow if you've got tens of thousands of records. If you've got coding resources, you might be better off with writing a batch delete program