Hi everyone,
I have an application that uses iBO. So far it was working ok with iBO 10x and 15.1.3.x but when I tried it with 15.2.0.2229 I started to have problems submiting purchases.
At this moment I only tried paying products and dues renewals, getting the following errors:
 
Err Num: 1000 - Source: (iboSubscriptions.CSubscriptions.Save):  Unknown error. Description: ActiveX component can't create object
Err Num: 1000 - Source: (iboOrders.CStdOrder.Save):  Unknown error. Description: ActiveX component can't create object
 
It's most likely the same issue, but I can't undestand why it stoped working, and I can't debug deeper than those metods invocations.

I've already tried reinstalling iMIS and iBO, checking if the dlls in Windows/system are the correct ones, but the problem remains.
 
Any thoughts?
 
 
Thanks in advance

Hello, does anyone know how to remove the "Messages" text from the password recovery page? This is displayed on the message iMIS gives after you enter your username. There is a block of text on this page that iMIS lets us update via the admin panel, and that is fine, but there is a title here called "Messages" that we cannot access and our client would like us to change it.

Any help would be much appreciated.

I am looking for equivalent code using web services only to get the WCM user from either a cookie or the session if possible.

Within a product we are using COM based iBO code for processing of registrations.  For some clients we have included the capabilities to include discounts on the registrations via discount functions containing a negative amount to offset the cost of the registration in other functions.

For example:

Main Registration = $100, Discount = -$20, Total Cost = $80.

This code is within a product we created and is not using eSeries any other components other than iBO.

Is it possible to add a custom action button at the top or bottom of a desktop form, say the Fundraising Enter and Edit Gift form? I know it's possible to add a link in the left navigation (the task area) but I'm more interested in the form itself.

For context: we're building a "cancel gift receipt" feature to clear out the receipt # and the best user experience in my opinion is to add that option on the same screen where the user is viewing the transaction.

I'm creating a custom CC processor for iMIS that will be used by Chapter administrators. The gateway will be the same for all chapters but each chapter will have their own account. Is there a definitive list of the value names passed in the name/value string? Can the string be manipulated based on settings in iMIS? For example, can I add "ORG=[selected org name]" to the value string based on the currently selected or logged in user, or are all the parameters fixed?

Greetings,

I've been reading documentation found here concerning the SmartControl and Business Objects.  I've read about writing typed classes to represent the BO. 

I'm primarily interested in binding the smart control to the CsContact business object.  I see I can accomplish a lot of the coding in conjunction with IBO.net.

I'm just looking for a little clarification on what smart control properties need to be set  in order for the binding to work.   I understand there is a BoundPropertyName

Has anyone retrieved data from the documentmain.blob field?

I have a client that would like to pull the data from this field into another website.

Just interested in the level of effort to do this.

Greetings all,

I'm having some trouble with the Secure.dll file, specifically with the Secure class, on an iMIS 15.1.x installation, using iBO.Net.

On my local machine, I'm able to instantiate an object of the Secure class, encrypt/decrypt data without any problems, etc. However, when I move the code out to my production environment (it's on an intranet), I keep getting a null reference error in the Secure.cs file, which I'm guessing is the name of the .cs file compiled to make the DLL. Specifically, I'm getting the following:

Has anyone written an API for CMS Express Engine?

We are looking for iMIS 15.2.