Hi, posting your question twice isn’t really going to help get it answered any quicker … and especially not when the answer to your question lies within the very same thread you asked the question in
I was wondering if there is any tool that can document by report name, the corresponding classes/objects & the table/column name. i.e. Excel with report → class/ objects used → Table.column name? The reason for this is I am looking at 250 odd XIR2 reports that needs documenting.
Assuming you mean full client reports, look here … List objects used in a series of reports. If you mean WebI reports, there is also a WID Scanner tool here in BOB’s Downloads.
The full client utility will document the classes / objects used, but not the tables / columns directly. Remember, a single universe object could reference many tables / columns. That said, you could use the output from the full client documentation and link it (on your own) to the universe documentation, and get very close.
while running the excel sheet for XIR2 which u posted the execution was failing at the end so can you please check and send me the correct one
it would help alot for me
While I could be available to do some custom work for you, I’m fairly sure you won’t like my rates!
That said, if you could give me a few more details than “was failing at the end,” I’ll be glad to see if there is anything wrong in the utility itself. Please include what version of the utility, and what version of Designer you are using.
If you are double-clicking the button and getting a code page, it means Excel is in Design mode. Turn off Design mode, click the button once, and it will execute.
I am also getting a error in the ListObjects() : VBAProject -7 : Out of Memory. I made the change suggested above and I still get the error. The universe is 871kb in size; I saved universe as text document and none of the objects look too long
A few people have reported an “out of memory” error, but no one has ever provided a repeatable example I could research. All I can suggest is standard debugging techniques. Try it on a co-worker’s machine to try to eliminate a corrupt installation. Turn off the error handling in the code, and step through line by line to try to find the culprit. Not the answer you hoped for I’m sure, but without more concrete information that’s all I can offer.
I think the size of my column names might be a factor - they all have table names tacked on the front of them. If it would help, I could send you a copy of the universe for you to research? I was able to re-produce the issue when I tried to document the universe on my laptop
I am having a similiar issue… when i use the tool on a smaller universe, it works perfectly, however, when I try to use this on a much larger, and more complex universe, I get this error. The only difference is that my error says ListContexts not ListObjects.
Can someone tell me what the solution is for this error?
Comment them out, and run maybe one at a time. In your case, run only the ListContexts line. See if it runs then.
Honestly, I’m still suspicious of simply “too large / complex” of a universe. I have a universe with 10,000 objects, 1,000 joins, and 200 contexts, and it runs just fine. I still suspect it is something about the particular “thing” being looked at, but let’s see if the debugging turns up anything.