I have a client who wants a list of a particular member type (REG) who reside in Canada or in Washington State.

This is really easy to do with SQL: SELECT Full_Name, ID, State_Province, Country, Member_Type FROM Name WHERE STATE_PROVINCE = 'WA' OR COUNTRY = 'Canada'

I tried using IQA in the following ways:

1. Create a query where I use the CsContact BO and Filter Member Type = "Regular" AND State Province = "Washington" OR Member Type = "Regular" AND Country = "Canada" Depending on the order, I either get all Washington or All Canada, but never both.  If I try Member Type = "Regular" and State Province = "Washington" or Country = "Canada" I get the same results, depending on the order
    
2. I tried creating two queries - one where Member Type = "Regular" and Country = "Canada" and one where Member Type = "Regular" and State Province = "Washington" then used left outer joins to the CsContact BO for each of them, but got multiple lines for each result and only ID numbers, no other fields
    
3. I created a query to just show Member Type = "Regular" and then used it as my source for a query where Country = "Canada" or State Province = "Washington" and was able to get only Canada and Washington but for every member type.

The only solution I could find was to use State Province and select all the Canadian provinces as well as Washington.  This works for now, but in the future they will be asking me for this type of thing again and it may not be possible to make the filtering selections from one field.  Did I do something wrong with my joins or my filters?

I have a client who wants to use an underscore in the alias name - something like Home_Country but when the query is run the underscore is stripped out. I understand that the underscore is used in keywords and that may be the reason.  Is there an escape character that can be used to preserve the underscore?

Thanks!

I just wanted make a comment about IQA in iMIS15. The navigation through and around IQA in iMIS15 could be a lot better.

For example…Why can I only get to the ‘Report’ option after editing an IQA and its opened in its separate window?

AND After running an IQA, why do I have to go all the way back to the beginning by clicking on IQA on the side menu? Why can't I be able to close the report or easily return to the last IQA folder I was just in?

I have attached a link to a brief video that demonstrates this issue.

Essentially, when using an IQA query that has been set up to return details to the Customer Portfolio, the query runs, the list is generated in an IQA window and a record is selected.  When this occurs, the results set is returned to the results  pane in the imis customer portfolio, but the cust portfolio is completely inactive.  You cannot enter a new record, select a record from the results set, no record is returned to the customer screens, etc.

When we export a document (IQA query, business object, content, content type, etc.) today, if that document has custom permissions it will not import into a database that didn't already have that content with custom permissions.  This comes up in the following scenarios:

• Create a new query in Dev, set permissions, test, copy to production.
• Create a generic iPart with permissions, import to new clients.
• Modify the ACL for a query to include a new Role in Dev, then import to Test.
• Import new Nav items we've set up in Dev.

Beside all that, we often have to apply the same permissions over and over to multiple items.  Having our own predefined security sets would make this a lot simpler.  (It would also keep the Access* tables from growing excessively, since each "custom set" is assigned its own key.)

We have an IQA that members can use to search for other members who fit a particular criteria - based upon specialty.  We want to then be able to select one of the returned company records and then drill down to another IQA that would list all that members areas of expertise.  Is that something that can be done?  I know we can like back to the actual ID and member record, but we want to drilldown to another report.

Hi people.

In 10.6  our users run an ADHOC query to identify which records they have touched during the day to produce labels to post out their results..

In this case the Name_Results_Summary  table where their username is entered into the table in the updated_by field.

Here is the username element fo the adhoc..

Name_Results_Summary.UPDATED_BY = Substring(user_name(),1,Case when charindex('_',user_name()) > 0 Then charindex('_',user_name())-1 Else len(user_name())End )

Hi,

I have two NetContact Business Objects, holding firms and employees, linked via a CsRelationship Business Object. I want to first collect all the firm records in  which have the relation type 'CR_PARTN', and I particularly want to keep track of firms that DO NOT have a relation of type 'CR_PARTN' (for them, the CsRelationship.Relation field will be NULL). I then want to link all of these firm records on the left-hand side to the employees in the second NetContact, matched by CsRelation. I should hopefully end up with a collection of firms linked by the relation CR_PARTN to employees and some firms with NULL relations, meaning that they do not have any CR_PARTN relationship with any employee.

I've hit a little snag with UD_Tables, and I'm not sure the best way to recover.

I'm in a prototype database for a rather large client (implementation in progress).  Early in the design, we added a number of UD tables with the fields they wanted.  In addition to the standard business objects (e.g. CsName_Demo), we created a couple of custom ones.

As the prototype evolved, we discovered some of the fields weren't needed anymore.  Our normal MO for removing fields (bad habit, I know) is to remove them from Define Tables, then touch all the windows based on those tables, which cleans up the orphaned fields.  This time, we got a PK violation on UD_WindowFields.  Apparently, iMIS now only deletes rows from UD_WindowFields if they exist in UD_Field.  I cleaned up the orphaned fields through SQL and the windows worked OK.  That problem is solved, and desktop iMIS is (mostly) happy.