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!
|
| |
| |
|
Re: Change data in system 
Posted: 01 Apr 09 1:54 AM
|
For example:when i change the opportunity record,the saleslogix write in MODIFYDATE field (table OPPORTUNITY) the data on GMT.I want the data in GMT+01.00.
Now,the data of saleslogix is two hours back because we use the DST
|
|
|
|
Re: Change data in system
Posted: 01 Apr 09 2:04 AM
|
Ah - you meant 'date', not 'data'.
As far as I know, the updating of those special fields is done within the SLX OLEDB Provider and I really do not think it is a good idea to interfere with this - even if you could.
Better to leave the datetimes as GMT and work out why your computers are not performing the translation from GMT to your timezone correctly. Have you got the Automatically Adjust for Daylight Savings (or whatever it is called) setting turned on?
|
|
|
| |
|
Re: Change data in system
Posted: 01 Apr 09 3:14 AM
|
What version of SLX?
What timezone are you in?
Are all users having the same problem?
Sorry for all the questions ... |
|
|
|
Re: Change data in system
Posted: 01 Apr 09 5:01 AM
|
version 7.2
timezone is 105 (GMT +1)
I work in saleslogix for integrate with erp and i compare the date for update the data |
|
|
|
Re: Change data in system
Posted: 01 Apr 09 5:35 AM
|
So you problem is not with SLX, but with the fact that timed data is always stored in GMT format - and when you compare it with the dates on your ERP system, which, presumably, are not in GMT format, the comparison sometimes gives inaccurate results?
In your integration module, are you connecting to SLX using the SLX OLEDB Provider? That should take care of the whole thing for you. If you cannot do this and you have to connect using the SQL Server provder, I suggest that you write a SQL Server UDF which takes as its argument a GMT datetime and returns a datetime adjusted for your timezone and use this for your ERP comparisons.
Phil |
|
|
|
Re: Change data in system
Posted: 02 Apr 09 7:52 AM
|
I'm glad I watch these forums...
We ran into this same issue. Ended up doing exactly what you've suggested (working around it in our sql code) because we are using the SQL Native client to connect.
We did all this long before we really knew anything about SLX, so...
| ...are you connecting to SLX using the SLX OLEDB Provider? That should take care of the whole thing for you. |
|
...this certainly clears up the issue for me.
| ...If you cannot do this and you have to connect using the SQL Server provder, I suggest that you write a SQL Server UDF which takes as its argument a GMT datetime and returns a datetime adjusted for your timezone and use this for your ERP comparisons. |
|
Now that someone has clearly stated how it works, as we transition to services based processes for our integration (replacing the hard coded ties that we used for expedience) - I know that I can switch to using the SLX OLEDB provider and won't have to include the "adjustment" anymore. |
|
|
|
Re: Change data in system
Posted: 02 Apr 09 8:13 AM
|
Cool - sounds like you completely grasped the ramifications & good luck.
I suggest that you do some testing with the SLX OLEDB Provider to ensure that:
a) You can connect OK - should be a non-issue, but you'll have to store username (use ADMIN) and associated password somewhere to be able to connect.
b) The commands which you are executing over the SQL Native Client connection work OK via the SLX Provider, which implements only a subset of the SQL available via a native connection. Fancy modern T-SQL is not implemented.
Phil |
|
|
|
Re: Change data in system
Posted: 06 Apr 09 4:15 PM
|
While writing to SLX through the SLX OLEDB providor is recommended, if you must set createdates, etc with T-SQL, GETUTCDATE() will return the current UTC date/time.
|
|
|
|