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!
|
|
Storing the values to the History Table
Posted: 08 Jul 08 7:00 AM
|
Hi,
In 6.2 Lan client for the controls we have a property called RecordToHistory.
Whenever we change any value, this record will be saved in history table with old value, new value, modified user and modified date.
Do we have similar property in 7.2 webclient.?
What should we do to store it in the history table..
Thanks,
Prathima |
|
|
|
Re: Storing the values to the History Table
Posted: 08 Jul 08 8:05 AM
|
Hi,
You would have to code it yourself - you can set a c# code snippet to run on saving, or you could put an onchange event on the required property to record it to history.
Thanks,
Nick |
|
|
|
Re: Storing the values to the History Table
Posted: 08 Jul 08 10:31 AM
|
Yes, in the web client you do that at the entity level. On the entity, you'll see a checkbox called "Audited". Check this box for the entity, and then check any properties on the entity you want to record changes for. Then on the "Extended" tab of the entity, you'll see a field labeled "Track History To". Enter "IHistory" there (you can select it from the drop down). Now, any of the "audited" properties will record their changes to history (the audited checkbox for the entity can turn it all on or off for all properties on the entity).
BTW, you can create your own tracking tables to do this as well (instead of using history). I've outlined how to do that here: http://customerfx.com/pages/crmdeveloper/2007/12/31/Creating-Custom-History-Tracking-Tables-for-Entities-in-SalesLogix-Web.aspx
-Ryan |
|
|
|
Re: Storing the values to the History Table
Posted: 09 Jul 08 6:10 AM
|
Originally posted by Ryan Farley
Yes, in the web client you do that at the entity level. On the entity, you'll see a checkbox called "Audited". Check this box for the entity, and then check any properties on the entity you want to record changes for. Then on the "Extended" tab of the entity, you'll see a field labeled "Track History To". Enter "IHistory" there (you can select it from the drop down). Now, any of the "audited" properties will record their changes to history (the audited checkbox for the entity can turn it all on or off for all properties on the entity).
BTW, you can create your own tracking tables to do this as well (instead of using history). I've outlined how to do that here: http://customerfx.com/pages/crmdeveloper/2007/12/31/Creating-Custom-History-Tracking-Tables-for-Entities-in-SalesLogix-Web.aspx
-Ryan |
|
Nice one Ryan! I was hoping there was an easier way to do it I didn' t know about  |
|
|
| |
| |
|
Re: Storing the values to the History Table
Posted: 23 Feb 10 9:40 AM
|
Originally posted by Veronka Capone
Ryan,
Thanks for the tip. Is it possible to do the same on LAN? How can I record changes in my own tracking table and on LAN?
Thank you. |
|
On the LAN, to store changes on your own table you need to code something of your own from scratch. There is nothing built in to facilitate this on the LAN client.
-Ryan |
|
|
|
Re: Storing the values to the History Table
Posted: 26 Feb 10 8:50 AM
|
Ryan,
I was thinking the quickest is to have a SQL trigger on History table, which will call a .dll. which will hadle insering the Old/New value stuff into the appropiate tables. When tryimg to run SQL assembly from SQL server I am getting this error:
The 'SLXOLEDB.1' provider is not registered on the local machine.
- I insatlled the SLX provider on the SQL server.
- SQL server is a 64 bit machine
- I retsarted SLX service on the SQL server
I am trying to avoid changing every single form on the LAN to audit fields. Any other idea?
Thanks ! |
|
|
|
Re: Storing the values to the History Table
Posted: 26 Feb 10 8:55 AM
|
The problem is that you're attempting to use the SLX Provider from something running as a 64-bit service (SQL Server). The SLX provider is 32-bit only and won't be seen from the 64-bit world.
I am not sure if it would work to compile the dll specifically for 32-bit but then call it from the 64-bit SQL server. That is what I would try (and if that works you could run it out of process and just spawn it from SQL).
BTW, do you need this logging table to sync? If not you could just skip using the SLX provider to do this.
-Ryan |
|
|
|