Focal Point
[FIXED IN 8200] Troubles trying to index hold tables within InfoAssist:

This topic can be found at:
https://forums.informationbuilders.com/eve/forums/a/tpc/f/7971057331/m/3447078976

December 18, 2015, 05:09 PM
CoolGuy
[FIXED IN 8200] Troubles trying to index hold tables within InfoAssist:
Hey all,

So, we have a scenario where we are trying to start having some "advanced" users that have access to build reports, etc. within the InfoAssist product. The first report I've assigned our first IA user is a multi-step request that contains multiple hold file requests joined together to prepare for the final report request at the end. Within the first 3 hold file requests, we are needing to index on a certain explicitly declared column/field. For some reason or rhyme, InfoAssist is not letting us do that. The procedure's request structure is as follows within the Query Panel within InfoAssist:


focusFile1 (mssql description file) still need index on column, option not visible in query pane
focusFile2 (mssql description file 2) still need index on column, option not visible in query pane

join focusFile1 to focusFile2 (should be on indexed columns)

focusFile3 (focusFile2) still need index on column 
**Note: The Index option appears for the above focusFile3 hold request (not for the above 2 requests), but doesn't allow us to use the fields we select for the index. I get an "invalid dao-object" message pop-up.**

join focusFile2 to focusFile3 (should be on indexed columns)

focusFile4 (focusFile2)

finalReport (focusFile4)



Anyone here know how to index columns for a hold request within InfoAssist? Also, anyone else run into the "invalid dao-object" error message before, and know what it means?

Any and all help is much appreciated!

Thanks in advance!

This message has been edited. Last edited by: CoolGuy,


8.2.02M (production), 8.2.02M (test), Windows 10, all outputs.
January 15, 2016, 06:06 PM
CoolGuy
UPDATE:

My case worker from IBI notified me that this was already an ongoing project within the product division and will be fixed as of 8.2.xx (scheduled to release on September 30th, 2016).


8.2.02M (production), 8.2.02M (test), Windows 10, all outputs.