**Note: I've posted this to the InfoAssist forum thread as well, but reposted here due to the lack of use of the InfoAssist thread for added post exposure.**

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,

I assume you can't do this.

How to Use the EXTERNAL INDEX Subcommand

Another option would be to build a "View" so your users wouldn't have to join these hold files together.

I would say that's pretty "advanced" for a user to have to combine their own hold files.

Can you do joins at metadata level?

Hi all,

To clarify a bit with our situation, we are seeking to restrict our "advanced" users to the InfoAssist product where they can work from metadata we've assigned them access to, but with no access to code. So, everything they need to accomplish should be/needs to be able to be done within the InfoAssist GUI tool. The only thing we've ran into a problem with is the ability to index focus-based hold files we are seeking to create within the tool. The online docs state one should be able to index with that type of hold file, and that that option appears within the query pane of the tool when working with that hold file type. It does not 100% of the time. It does appear for one out of three focus holds within the report we are trying to replicate from our old 7.x environment, but when we seek to add a field as the index we get the "invalid dao-object" error.

Thank you for the suggestions you've shared thus far, but we really want to be able to allow our "advanced" users to accomplish the holds on their own within InfoAssist so we don't have to manage the data prep/view creation for every little report request someone might want to make. We would give them code access, but we have no way to restrict SQL out statements. We can turn SQL out off for everyone including us, but not at a security group or user basis that we know of.

Anyone here have any experience with indexing columns within the InfoAssist tool that has overcome these issues I've been describing? Or, does anyone know how we could lock down SQL out statements for select groups or individuals?

Any help or insights are much appreciated.

Thanks in advance!

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).