10/10/2024 2:11:02 AM
slxdeveloper.com
Now Live!
|
|
|
User Profile -
Konstantin Vishnevsky
|
|
|
|
Konstantin Vishnevsky Coram Inc.
fjrigjwwe9r1SiteUser:UserBio fiogf49gjkf0d
|
|
Log in to send this member a
message! |
|
|
Konstantin Vishnevsky's
Contributions |
Konstantin Vishnevsky
has contributed
comments and
0
articles.
|
|
Select to view:
|
Comment: Re: SalesLogix Synchronization Report
fiogf49gjkf0d Yes sir, we are talking about ZIP files :) No wonder many of my users were marked as non synching and we couldn't understand why is that.
But your report is a very useful utility, we are using it constantly. Thanks for providing the code!!!
Author: Konstantin Vishnevsky - 11/27/2007
|
|
Comment: Re: SalesLogix Synchronization Report
fiogf49gjkf0d Mike, I beg to differ. I can send you a TEF I have ran across yesterday. It's Created date: Wednesday, November 21, 2007, 3:01:29 PM, but the Modified date: Wednesday, May 23, 2007, 1:08:06 PM I spoke to Paul Hubbard, SAGE Customer Support Manager and he informed me that this may be the case. Here's what he said in his email:
The ZIP- tells me this is (or was?) an attachment. The dates most likely mean the file compressed in the TEF was probably last modified on May 23, but the TEF file being viewed was created on Nov 21. I've seen that behavior outside of SalesLogix, I believe it was with a PDF file inside a Zip file.
Author: Konstantin Vishnevsky - 11/27/2007
|
|
Comment: Re: SalesLogix Synchronization Report
fiogf49gjkf0d Mike, please correct me if I'm wrong, but wouldn't it make more sense to use DateCreated instead of DateLastModified? The reason is that if the file is a ZIP and it contains, let's say a PDF document from a library that was created in May, DateModifed shows of a PDF file and not the Sync file itself, thus showing in report that user has not synced since May.
Author: Konstantin Vishnevsky - 11/27/2007
|
|
Comment: Re: SalesLogix Synchronization Report
fiogf49gjkf0d Just tried this script on my app server. Since the sendmail option doesn't always work (as in my case), we had to find a workaround (works only on Win2000 Server and Win2003 Server).
Instead of:
[code]
' Create a new SMTP message object Set msg = CreateObject("SendMail.Message") ' Create a new SMTP message object 'Set msg = CreateObject("SendMail.Message") ' Set the message properties 'msg.RecipientEmail = "name@email.com" 'msg.SenderName = "SalesLogix Sync Report" 'msg.SenderEmail = "name@email.com" 'msg.Subject = "Weekly SalesLogix Sync Report" ' add the report to the message body 'msg.MessageHTML = strReport ' Send the message 'msg.Send "10.0.0.4" [/code]
I used
[code] Set objMessage = CreateObject("CDO.Message") objMessage.Subject = "Weekly SalesLogix Sync Report" objMessage.From = "name@email.com" objMessage.To = "name@email.com" objMessage.HTMLBody = strReport '==This section provides the configuration information for the remote SMTP server. '==Normally you will only change the server name or IP. objMessage.Configuration.Fields.Item _ ("http://schemas.microsoft.com/cdo/configuration/sendusing") = 2 'Name or IP of Remote SMTP Server objMessage.Configuration.Fields.Item _ ("http://schemas.microsoft.com/cdo/configuration/smtpserver") = "10.0.0.4" 'Server port (typically 25) objMessage.Configuration.Fields.Item _ ("http://schemas.microsoft.com/cdo/configuration/smtpserverport") = 25 objMessage.Configuration.Fields.Update '==End remote SMTP server configuration section== objMessage.Send [/code]
Author: Konstantin Vishnevsky - 12/7/2006
|
|
|
|
|
|
|
|