Eric, I was assuming there was one cookie that stored both the currently logged in ID and the currently selected ID. The cookie that I meant was the one that the current iparts look at - for example, the IQA iPart allows you to base the results of an IQA query on either the currently logged in ID or the currently selected ID - I assumed these were both held in the same cookie in the web view.

So, taking the thinking over into the desktop view - I know that the framework in the desktop is the same as the web view (login, navigation etc...). When you login to the desktop view, there is a cookie that the currently logged in ID is written to, and the currently selected ID defaults to the ID of the person currently logged in. If you create an IQA iPart in the desktop currently, and you link the results to the currently selected ID, it will always pick up the currently logged in ID. So, I assume that the cookie that the iPart looks at is there, but the currently selected omnis ID is not written to the cookie when the selection is made in omnis.

My idea for a workaround involved not making the selcetion in omnis, but rather in a .net page. Specifically, the Customquery page that we created to show IQA queries. The selection is made on this page (by hitting the "select" link in the query) - the results are then carried through to omnis and the results then show in the customer portfolio.

So, in theory, because you are making the selection in a .net page (and not actually in omnis), it should be possible to easily write the selected ID to the cookie, before the omnis customer portfolio loads.

I haven't seen the code for the IQA iPart, but if it's using the standard methods, you should be able to set the needed cookie using the code below. The "userID" variable needs to contain the iMIS ID for the person you are selecting. You will probably need to modify the CustomQuery page to raise an event rather than directly sending the user to the special URL; you'd need to handle that event, run the code below, and then do a Response.Redirect to the special URL.

CDataAccess da = new CDataAccess(ConfigurationManager.ConnectionStrings["DataSource.iMIS.Connection"].ConnectionString);
da.OpenConnection();

Asi.Bae.Business.Customer.User user = new Asi.Bae.Business.Customer.User(userID, da);

Secure sc = new Secure();

// Set Up Cookies for user
Response.Cookies["UserID"].Value = sc.Encrypt(user.Id);
Response.Cookies["FirstName"].Value = user.FirstName;
Response.Cookies["LastName"].Value = user.LastName;
Response.Cookies["FullName"].Value = user.FullName;
Response.Cookies["Company_ID"].Value = user.CompanyId;
Response.Cookies["Email"].Value = user.Email;
Response.Cookies["Organization"].Value = user.Company;
Response.Cookies["SecurityGroup"].Value = user.SecurityGroup.Equals(string.Empty) ? sc.Encrypt("None") : sc.Encrypt(user.SecurityGroup);

// If selecting themselves then they are no longer "impersonating"
if (Asi.ContentManagerNet.SessionState.User.ContactId == user.Id)
{
 Session["Impersonating"] = null;
 Session["ContactKey"] = null;
}
else
{
 Asi.Business.Contact.Individual individual = Asi.Business.Contact.IndividualController.Individual(user.Id, StatefulBusinessContainer);
 CurrentContext.SubjectUniformKey = ((individual)).ContactKey;           
 Session["Impersonating"] = true;
 Session["ContactKey"] = CurrentContext.SubjectUniformKey;
}

Eric Means
System Architect, ASI

what system imports are used for that ?  I thought it was just "ASI.Bae  "

I am using the same code i.e:

CDataAccess da = new CDataAccess(ConfigurationManager.ConnectionStrings["DataSource.iMIS.Connection"].ConnectionString);
da.OpenConnection();

but I get "Type CDataAccess is Not Defined" error.  (??)

thanks.

Just reference the CDataAccess.dll file. That class is not in a namespace.