happens at line 55 of MarkupAdjustment.adjustInvoice().
Here's the line:
inventTrans.inventTransId == vendInvoiceTrans.inventTransId &&
inventTrans.dateFinancial == vendInvoiceTrans.InventDate &&
inventTrans.invoiceId == vendInvoiceTrans.invoiceId &&
inventTrans.statusReceipt == StatusReceipt::Purchased &&
inventTrans.statusIssue == StatusIssue::None &&
inventTrans.packingSlipReturned == 0 &&
! inventAdjustAllocate.isAllocated(){
...
}
The weird thing is it only happens on the first Markup Adjustment of the
day. Others adjustments during the day are done in seconds. It's like
if the first one has to cache the query and during the rest of the day
the query is taken from cache.
To help this, I'm planning on adding an index on InventTrans with those
fields:
inventTransId
dateFinancial
invoiceId
statusReceipt
statusIssue
packingSlipReturned
Yes, it looks like a big index. That's the problem, I've reed that
indexes improve select but hurts update and insert statement since the
indexes has to be calculated. How bad will it hurt insert and update
since InventTrans is a table with a lot of rows (719236) and the index I
want to add is big.
Regards,
Steeve...
| Yahoo! Groups Sponsor | |
|
|
Yahoo! Groups Links
- To visit your group on the web, go to:
http://groups.yahoo.com/group/development-axapta/
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
