InaPlex Forums

Greetings - I am curious as to how much effort is involved in converting Inaport 6 profiles to run on Inaport 7.  It was fairly challenging to move from In5 to In6.  How do the two conversions compare?

 Also I am assuming that Inaport 7 is fully compatible with Goldmine 8.0 - eh?

Hi

V6 profiles can be opened and used in V7 with no conversion.

V5 to V6 was a big job for GoldMine users (but not for SLX and CRM) because the fundamental model of how the table maps were set up changed dramatically. This has not happened with V6 to V7. The benefit of the change was that it became much more powerful and flexible.

Any other questions, please ask

Thanks - thes econd part of the questions was whether or not Inport 7 (and 6 for that matter) are compatible with Goldmine 8 (PE)?  Do profiles need to be tweaked for that?

 Also is their a new license fee for Inaport 7 - or does the Inaport 6 license work?

Hi

Sorry for missing that. Yes, Inaport V7 is compatible with GM 8/PE. Profiles should work unchanged.

No the V6 license does not work - you will need a new license. To get one, go to Purchase - Get License - Software Assurance Renewal. You will need the current inaport license number (LIC12345678) and the GodlMine license number used when you purchased. If your Software Assurance has expired, you will need to get it current to get a new license - cost will be advised.

If you are also upgrading GoldMine, you will have a new GM license number. Do the above procedure to get your Software Assurance current, then conatct support@inaplex.com - we will replace the license with the new GM license number.

Thanks again - Also one last question I was wondering if a particular bug in naport 6 was fixed

We run about 20 different porfiles against 26 different databases (making about 500 Inaport profiles that we run nightly).  However when we upgraded from In5 to In6 we had one profile that gave erratic results in In6. So we left it in In5 at that time.

 Now we are upgrading to Goldmine 8 and I have read in other posts that In5 is not compatible with GM 8 - so we will have to resolve the problem with this particular profile before we go forward.  We currenly run the most recent release of In6 and still have the problem with this profile.

The Select statement is causing the problem - it works fine in In5 but not In6 - do you think In7 has fixed this problem

select * from ps_history where not exists            
(select linkrecid from conthist where PS_HISTORY.gm_donation_id =            
conthist.linkrecid) and PS_HISTORY.gm_date is not null

Hi

That is a lot of profiles! I encourage you to have a look at the logging capabilities in V7 - they have improved a lot, and may be relevant to you.

I do not understand why that query would work in V5 and not V6. In either case, the SQL is simplay passed to the OLEDB provider for the data source (which I assume is SQL Server in your case).

I suggest you run a test with V7, and if you have problems contact support; you will be asked for a debug log, so maybe do that first.

Regards

David