When using IQAs there are many things we can do with them and many others we cannot or shouldn’t. As any graphical front end, there will be limitations to what can be done. Let’s first discuss things that you cannot and shouldn’t do in IQAs.

1.) Custom SQL scripts cannot be used unless custom views are created in the database and added as business objects. Try to avoid adding custom views if possible.

2.) Multiple nested loops/joins since this increases the time to complete the query exponentially. If you have long running queries, check to see if this is the problem.

3.) IQAs are only for reading from the database, to write to the database you must use some kind of form implementation such as Sonic Forms or iMIS Form Builder.

Now here are some basic recommendations to remember when building IQAs.

1.) When looking for individual members use their unique IDs rather than names, usernames, or emails. You can use those other fields to help find the member you are looking for but remember they are not unique, and you can have multiple people with similar names.

2.) Set the correct security permissions for the IQA so the right users have the permissions to run the query.

There is far more IQA functionality than can be covered in a short article, so I recommend everyone working with IQAs to go through the ASI documentation and tutorials to get a better grasp of how they work here. For over 25 years, E-Tech has been consulting, hosting and maintaining iMIS clients, if you need any assistance please feel free to Contact Us.

In iMIS you are often forced to use direct tables or views in IQAs and Business Objects if you are looking for something. Tables contain the raw information but, sometimes you need information which is stored in multiple tables and do not wish to spend time formatting and pulling in data from different tables; this is where views come in and can be used to speed things along. Here are some views that contain information that will be useful when creating IQAs and business objects.

Views Related to Users

Login – Contains information related to a user’s login information, such as login ID, iMIS ID, username, full name, and company name

Name_All – Contains all the name information about the contacts including their address and company

vBoContact – Contains the contact status code with the name of the contact

vBoIndividual – Similar to the contact view, but contains more information on the institute of the contact

vBoUser – Various views containing user keys, ID, login, emails and more. Look through each view to determine which one is best suited for your needs. vBoUserData is the table that would be most useful for most purposes

Other Useful Views

vBoDocument – This view is related to the documents that have been uploaded to iMIS so you can see the document keys and the name of the document

vBoSystem – These views contain various information related to the iMIS configuration, if you need to find what some setting is in iMIS look through these views to find what you need

For more information on iMIS database views or general information on iMIS, feel free to contact us.

When looking through your iMIS database you may see a lot of tables and not know what many of them are for. If you need to write custom SQL queries or do troubleshooting with some issues, it is quite useful to know what information is stored where. Here are some more tables to get you started.

Users Tables:

• ContactMain table contains all the contacts you have inside iMIS.
• GroupMain table contains all groups and organizations you have inside iMIS.

Website Tables:

• Content table contains the content used on the iMIS website. You can view when a content page was created, last changed by who, settings of the page and the location.
• DocumentStorage table contains information related to the documents that have been uploaded to iMIS. Related to the DocumentMain table but might contain more relevant information to you.

Transactions Tables:

• GatewayTransaction table contains transactions that have gone through the payment gateways.
• Invoice table contains invoice information.
• Order table contains orders requested. Includes failed and successful orders.

Misc Table:

• Error Table contains errors that have occurred and have been recorded to the database. An additional troubleshooting step if you need to check for errors. Usually, this table is empty.

For more information on iMIS database tables or general information on iMIS, feel free to contact us.

When looking through your iMIS database you may see a lot of tables and not know what many of them are for. If you need to write custom SQL queries or do troubleshooting with some issues, it is quite useful to know what information is stored where. These are some of the basic tables to get you started:

Users Tables:

• Users table shows you all the staff users that have been created.
• UsersMain table shows you all the created users.
• Name table contains the users and contacts and their personal information.
• Aspnet table contains various system information about user accounts.

Transaction Tables:

• Trans table holds all the transactions, and you can see the debit, credit description and for who the transaction was completed for.

System Tables:

• System_Params table holds the parameters for iMIS settings.
• System_Variable table holds the iMIS variables.
• SystemConfig table holds the configurations for iMIS.

Other Tables:

• Cart table holds the current carts of the users. You may sometimes need to delete all the carts to resolve some issues.
• CommunicationLog table is one of the biggest tables which holds all the email information that have been sent through iMIS.
• DocumentMain table is usually the biggest table and holds all the documents that have uploaded to iMIS in blobs.

For more information on iMIS database tables or general information on iMIS, feel free to contact us.