How do you force Adagio Ledger to re-index? I have a client where the drill down works for some items but not others. As in, the transaction detail shows for one transaction but not another. DIC comes up clear; we have auto-indexing turned on; they are on version AL20130726.

Is your client consolidating any accounts? You cannot drill down on a consolidated transaction. And by "transaction detail" I assume you are referring to the offsetting entries in the journal entry.

Consolidation is not allowed in the company profile and if we look at the posting journal the transaction detail is there.
Yes, by "transaction detail" I am referring to the offsetting entries.

Lyndon:
If you locate one of those problem accounts in the Chart of Accounts and view it, what is the setting for "Posting Format"? If it is "Consolidated", it will be difficult to see the other sides of the transaction.

Hi Lyndon

This is not an authorized solution but I have tried it and it works. Delete or rename or move the file GLPST'F.xxx and click on the Find Trans button under Inquiries | View Transaction. It will rebuild the index.

Steve

In the Ledger company profile on the Posting/Reports tab is an option called 'Auto build TX inquiry index'. With this enabled, the transaction lookup file (referred to by Steve in his reply) is rebuilt every time you post a batch. With this disabled, posting a batch will delete this file, and accessing the lookup function (either in Transaction inquiry or the Financial Reporter drill-down) will start to regenerate the index file.

This does not change any of the replies above if an account was consolidated.

The problem is restricted to Accounts Payable entries coming through to the Ledger. We are drilling down from the Bank account into the transaction detail. PayDirt entries show the transaction detail properly. Accounts payable does not have "prompt to consolidate" turned on.

Posting format of Payables master account is set to "detail".

Steve's solution worked! Thanks Steve!!! I owe you a drink at the next AOC.

Support:
That's interesting. Shouldn't DIC rebuild that index as a matter of course?

No, it's not an integrity error. And we give the users the choice to rebuild when then need it or when it changes (ie posting or unposting). If you build and index and don't post any Ledger batches, then the index doesn't require refreshing.

Hi Lyndon,

Since I know you copy files around a lot, I wonder if you picked up an old index with a new posted file. I also know that you rarely post any transactions in your office.

How do your clients have this set? Would you (or they) have turned off the index function after post?

Our procedure is to always copy into an empty directory. All clients have auto indexing turned on ( at least that is our recommendation). It was for this one.

Hi Steve,

We had this problem and your solution worked! (deleting the GLPST'F. file) You just saved us so much time!

Thanks so much!