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!
|
|
ChangeNode on Notes/History
Posted: 06 Mar 07 9:04 AM
|
fiogf49gjkf0d Anyone know how to get around the fact that onchangenode does not fire when the user uses the curser key to move between rows AND moves to a row previously off screen, which thus means that you cannot just down curser key through the notes/history reading the notes as when you start moving the grid downwards the notes no longer refresh?
Cheers
Nick
|
|
|
|
Re: ChangeNode on Notes/History
Posted: 06 Mar 07 9:16 AM
|
fiogf49gjkf0d This seems to work for me. What version of SalesLogix are you using? and what is your database platform? |
|
|
|
Re: ChangeNode on Notes/History
Posted: 06 Mar 07 1:10 PM
|
fiogf49gjkf0d You're right, that post was badly lacking specifics,
windows 2003 server
sql server 2000
SLX 7.0.1 (db was 6.1 been uppgraded this weekend)
I have not tested on my own v7 system yet, will try tomorrow and see if I can replicate it on mine.
See ya
Nick |
|
|
|
Re: ChangeNode on Notes/History
Posted: 06 Mar 07 1:15 PM
|
fiogf49gjkf0d I just tried it on a 7.0.0 system, and it appears you are correct. Once you get the item on the screen, you can hit up, then down again and it will change, but if you scroll of the screen, the notes do not change. I am running on SQL 2005, so it seems to be a bug in SalesLogix. It does work on our production 6.2.6 system. Good luck. |
|
|
| |
|
Re: ChangeNode on Notes/History - FIXED
Posted: 08 Mar 07 8:14 AM
|
fiogf49gjkf0d Kudos to Andrew Stephenson @ Sage who has found the following way to solve this issue ...
Simply tick the sortable property on the grid.
Three cheers for Sage tech support
See Ya
Nick |
|
|
|
Re: ChangeNode on Notes/History - FIXED
Posted: 10 Mar 07 12:25 PM
|
fiogf49gjkf0d Originally posted by Nick McLean
Kudos to Andrew Stephenson @ Sage who has found the following way to solve this issue ...
Simply tick the sortable property on the grid.
Three cheers for Sage tech support
See Ya
Nick |
|
FYI.. "Sortable" is a code word for.. loads the entire recordset into memory..
So if you notice a bit of memory footprint bloat.. that is why.
--
rjl |
|
|
|
Re: ChangeNode on Notes/History - FIXED
Posted: 12 Mar 07 3:16 AM
|
fiogf49gjkf0d oooh loading the entire notes/history recordset into memory thats not so hot then (especially since the client that has raised this issue with me has insisted that record to history be set on every field!
Oh well, fingers crossed it will not be too detrimental to them.
Cheers for the FYI
See Ya
Nick |
|
|
|
Re: ChangeNode on Notes/History - FIXED
Posted: 14 Mar 07 7:55 AM
|
fiogf49gjkf0d Record to history on every field!???!
That's going to break the back of the system! It was NOT intended to be a full audit mechanism.
Your client is NOT going to like the results. I'd get a disclaimer signoff ASAP!
--
rjl |
|
|
|
Re: ChangeNode on Notes/History - FIXED
Posted: 14 Mar 07 8:03 AM
|
fiogf49gjkf0d Ace - Thank you for that, I wanted to tell them something similar, but I didn't have the confidence to say it. You have given me the confidence to tell them that this is just too over the top. |
|
|
|
Re: ChangeNode on Notes/History - FIXED
Posted: 14 Mar 07 8:08 AM
|
fiogf49gjkf0d Is there a replacement to using record to history. Basically they feel that using record to history settles arguments as to who changed a field (especially when the person who did change it is denying changing it).
Could the SQL transaction logs be thwe answer to this? |
|
|
|
Re: ChangeNode on Notes/History - FIXED
Posted: 15 Mar 07 7:20 AM
|
fiogf49gjkf0d If they have issues where they are "fighting" over who changed what.. time to take their computer' away from them and give them a pad and pencil!
SalesLogix was not designed to do 100% auditing of 100% of the fields... plain and simple.
I'd suggest:
A - A limited audit of key fields
B - Implement team security and get rid of the EVERYONE security.. it's useless in this case ( It's always useless
You could go to adding (UGH) UPDATE Triggers on every (user) table.. and record it that way.. but even that type of an audit trail can be very messy..
NOPE.. you will have to get them to settle down and be friends.. ..
--
rjl |
|
|
|