Home | Forums | Contact | Search | Syndication  
 
 [login] [create account]   Wednesday, October 23, 2019 
 
View User Profile  

 User Profile - John Gundrum  
  John Gundrum
Self

fiogf49gjkf0d


Log in to send this member a message!
 


 John Gundrum's Contributions
John Gundrum has contributed 8 comments and 0 articles.
 
Select to view:    
Comment: Re: Creating SalesLogix Table ID Values - The Definitive Guide
fiogf49gjkf0d
Matt,

I was referring to the "production application server" that you referenced. Basically, any machine that will run an application that uses the SLX OLE-DB provider must have the SQL Native Client installed. Your last response stated "It only has problems on the Windows Server 2003 production server" so I would check to make sure that server has the SQL Native Client installed.

John G.

Author: John Gundrum - 5/29/2009

 
Comment: Re: Creating SalesLogix Table ID Values - The Definitive Guide
fiogf49gjkf0d
I have been unable to get the Provider code to work on our production application server (I get a 'Unable to initialize data dictionary.' error).

Matt,

Seeing the 'unable to initialize data dictionary' error I am wondering if the SQL Server native client is installed on the production server. I know from past experience that error would appear after installing the 7.x.x client without installing the SQL Server native client.

John G.

Author: John Gundrum - 5/29/2009

 
Comment: Re: Creating SalesLogix Table ID Values - The Definitive Guide
fiogf49gjkf0d
Just an update... I figured out the issue. Its two-fold actually. The first part of the problem is originating in the view. I found an article on SQL Server Central that describes the

Warning: Null value is eliminated by an aggregate or other SET operation.

message perfectly. It turns out my view had SUM aggregates where I didn't put a ISNULL() around the field to convert any NULL values to a 0. The warning is just what it says, it left that record out of the aggregate. After surrounding the offending fields with ISNULL() the SQL worked without a hitch.

I am still having an issue with the Provider not automatically generating the ID for the primary key field. Is there something else I need to do?

Thanks,
John G.

Author: John Gundrum - 6/29/2007

 
Comment: Re: Creating SalesLogix Table ID Values - The Definitive Guide
fiogf49gjkf0d
Auto-Incrementing ID fields in 7.0.1. I created a custom table and set the primary key field to auto increment. I am trying to do a insert from the Administrator but I am getting this error.

[6/28/2007 11:31:30 PM] The statement failed and returned the following error: "Warning: Null value is eliminated by an aggregate or other SET operation. : The statement has been terminated. : Cannot insert the value NULL into column 'C_OPPORTUNITY_HISTORYID', table 'SalesLogix.sysdba.C_OPPORTUNITY_HISTORY'; column does not allow nulls. INSERT fails"

I checked and double checked and auto-increment is checked for this field. Here is the insert statement I am using:

INSERT c_Opportunity_History
(estimatedclose, description, accountname, status, closeprobability, totalrevenue,
servicerevenue, totalgp, servicegp, invoicedate, invoicerevenue, invoiceproductrevenue,
invoiceservicerevenue, invoicegp, invoiceproductgp, invoiceservicegp, closeyear,
closequarter, closemonth, accountid, opportunityid, accountmanagerid, accountmanagername,
createdate, createuser, createname, modifydate, modifyuser, modifyname, asofdate)
SELECT estimatedclose, description, accountname, status, closeprobability, totalrevenue,
servicerevenue, totalgp, servicegp, invoicedate, invoicerevenue, invoiceproductrevenue,
invoiceservicerevenue, invoicegp, invoiceproductgp, invoiceservicegp, closeyear,
closequarter, closemonth, accountid, opportunityid, accountmanagerid, accountmanagername,
createdate, createuser, createname, modifydate, modifyuser, modifyname, asofdate FROM v_Opportunity_History

I am not specifying the primary field in the INSERT statement. Based on what I'm reading about the auto-increment ID checkbox the provider should automatically generate the ID for me. What am I missing?

Thanks,
John G.

Author: John Gundrum - 6/28/2007

 
Comment: Re: Crystal RDC Help Files
fiogf49gjkf0d
Ryan,

As always, thanks for all the help.

John G.

Author: John Gundrum - 2/13/2007

 
Comment: Re: Crystal RDC Help Files
fiogf49gjkf0d
Ryan,

Do these docs apply to Crystal XI R2 for SLX 7.0?

Thanks,
John G.

Author: John Gundrum - 2/13/2007

 
Comment: Re: E1 User Audit
fiogf49gjkf0d
Ok.. Found out some interesting aspects for this. The bundle specifically states to release the menu strip. Thats all I released. For this I released it to the the group Marketing and the team Sales Managers. In the test system I tested using the Admin account (my bad)

When I logged in as myself it was giving the error. Which prompted the previous message. I started fiddling around some and tried releasing the menu strip to Everyone since thats how I did it in the development database. This did not work and ultimately was not who neede to see this.

I knew the other plug-ins were not released. I decided to release the DBOpen active script. This solved the login issue. But now I got an error when opening the audit form from the menu. Now I went back to Architect and release the active form and ..... it all worked!!! So with some trial and error this is what I've concluded as far as releasing the individual plug-ins

E1AF_UserAudit - Release to selective users
E1AS_DBOpen - MUST be released to Everyone
E1MS_UserAudit - Release to selective users

John G.

Author: John Gundrum - 5/15/2006

 
Comment: Re: E1 User Audit
fiogf49gjkf0d
Ugh.. I tested this in our development database and all worked fine. Now I tried installing the bundle to our production database and when I logged in I get this error

An unusual error has occurred when executing System:E!AS_DBOpen. Contact your system administratot. 0x0 @0: ActiveScripts System:E1AS_DBOpen Exception: Could not load plugin System:E1AS_DBOpen

I released the menu strip and set the dbopen and checked it. All seems fine. I'll check again just to triple check.

Any ideas?

Thanks,
John G.

Author: John Gundrum - 5/15/2006

 


 
 slxdeveloper.com is brought to you courtesy of Ryan Farley & Customer FX Corporation.
 This site, and all contents herein, are Copyright © 2019 Customer FX Corporation. The information and opinions expressed here are not endorsed by Sage Software.

code of conduct | Subscribe to the slxdeveloper.com Latest Article RSS feed
   
 
page cache (param): 10/23/2019 8:29:54 PM