The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
|
|
issues regarding migration...! 
Posted: 09 Jun 08 11:47 PM
|
Hi,
We have migrated SalesLogix from 6.0 to 7.2 and its using Oracle database.
We are facing 2 issues out here
1. When we open a plugin window in the architect it gives error “Companyversion currently Float : expecting string” we have checked it and its not float its Number.
because of this error its not showing any of the plugin.
Is there any way to come out this other than changing the schema of the database.
2. Its not showing any sales processes and stage in the database .
In opportunity all the data in the “stage” and “salesprocessid” field is blank .
and in salesprocesses table no record is available.
That’s why its not showing any of the previous stage and sales processes in the oppotunity.
thx in advance.
|
|
|
|
Re: issues regarding migration...!
Posted: 10 Jun 08 7:18 AM
|
A few questions:
a - 7.2 SP2?
b - What Oracle version?
c - Does the client OLEDB version exactly match the server?
d - Are there multiple db's in the same Oracle Instance?
I hope the answers are:
a - Yes
b - The latest supported version per Sage SalesLogix compatability docs
c - Yes
d - No
If not.. they should be.
--
RJLedger - rjlSystems
"...Customer First..." |
|
|
|
Re: issues regarding migration...!
Posted: 02 Jul 08 9:53 AM
|
We're having this same issue. I emailed the originator of this thread, Gaurang, asking him if he resolved the issue. His response is below. I've posted it for the benefit of others and to get some feedback weather this is the right solution for everyone. Is there any risk?
>> Yeah it got resolved just by changing the "COMPANYVERSION" field in PLUGIN table to STRING...!!
Thanks Gaurang and all!! |
|
|
|
Re: issues regarding migration...!
Posted: 11 Dec 09 2:10 PM
|
Just for the next person:
The plugin manager in Architect is giving me this error of "qPlugin: Type mismatch for field 'COMPANYVERSION', expecting: String actual: Float"
I haven't even migrated, upgraded, or even patched anything in almost 12 months and never had this issue until today.
We have version 7.2.2 and the SLX knowledgebase says this is a known issue with 7.2.2. The defectID is 1-63313 and the solution is to upgrade to 7.5.0. The Resolution ID: 498457 says it is a known issue while using an Oracle 9i database. The reason we did not move to version 7.5 when we upgraded last year is because we HAVE an Oracle 9i database and version 7.5 of SLX says it does NOT support an Oracle 9i database. So the Sage knowledgebase is basically telling me I can't do anything unless I upgrade our database to 10g --- which (according to our DBA) is not going to happen for a very long time.
So I hope your solution of altering the column from a number to a varchar will work, because that is what I'm about to do.
BTW - can we alter the table in the Database Manager in Architect? I don't see the PLUGIN table listed. So I guess I'll just do it manually through a SQL window. |
|
|
|
Re: issues regarding migration...!
Posted: 11 Dec 09 2:55 PM
|
Do you have any remotes?
The main concern to execute actions via the SLX tools is for syncrhonization.
If you have remotes, you may want to verify how the Plugin table is defined on them. If it is properly defined as a string, then there is no further issues to consider. If it is improperly defined, then you need to figure out how to correct it as well, as any plugins with a value that isn't a valid float would then also break your remotes.
|
|
|
|
Re: issues regarding migration...!
Posted: 11 Dec 09 2:57 PM
|
Do you have any remotes?
The main concern to execute actions via the SLX tools is for syncrhonization.
If you have remotes, you may want to verify how the Plugin table is defined on them. If it is properly defined as a string, then there is no further issues to consider. If it is improperly defined, then you need to figure out how to correct it as well, as any plugins with a value that isn't a valid float would then also break your remotes.
|
|
|
|
Re: issues regarding migration...!
Posted: 11 Dec 09 4:09 PM
|
So what is the data type and length in 7.5 ?? In my development DB I just made it a VARCHAR2(64), but I would like to know what COMPANYVERSION is when we upgrade.
We don't have any remote users and I hope we don't go to that with all these modifications I've made.  |
|
|
|
Re: issues regarding migration...!
Posted: 11 Dec 09 4:52 PM
|
On my 7.5.1 system, it is set as a FLOAT.
I also wanted to point out that you may need to also alter BASEDONCOMPANYVERSION. You may need to test and figure out if this is a problem or not for you, but typically, whenever you make a new version of a Plugin that was created by a Different Company (even if it is yoour own company, but if you don't have an exact match on your Options) it will put the original Company and Version values on the BASEDON fields.
|
|
|
|