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!
|
|
History Table Custom Field
Posted: 18 Apr 07 8:19 PM
|
SLX version 7
SQL Server 2005
My sales rep need to specify a product whenever they schedule an activity. I created a new field in the Activity Table and added that field to the Activity Detail view, I made changes to the Global activity script to move this data to a new field in the history table and it works fine.
However, when I add this new history table field to the History Detail view and when the user creates a completed Activity the value for this field is not stored in the DB. if I edit a existing history and modify the field the update is stored. How can I resolve this
I also thought of using the Category field for this purpose but, the category field has a field length of 64 and my data length is more than that
1) how can I increase the length of the Category field in the Activity and History Table to say 255
or
2) How can I make sure that when a new history is created (using completed history) the data is captured using a new field.
As always your help is appreciated
|
|
|
| |
|
Re: History Table Custom Field
Posted: 19 Apr 07 11:34 AM
|
fiogf49gjkf0d are there any other work arounds? Can we increase the length of the Category field? |
|
|
|
Re: History Table Custom Field
Posted: 20 Apr 07 8:12 AM
|
Yes you can... BUT remember, any changes to "core fields" is a non-supported action. You will have to do a couple of tricky things to do it since the SaledsLogix DB Manager (even in v7.0.x) does NOT support/allow making changes to core fields.. only adding new fields to core tables>
A - You need to "unlock" the field in question. If you know how to do this.. fine.. but If not, send me an email and I'll tell you how. It's one of those areas where you are "crossing the line".
B - Once unlocked then you can use the SalesLogix DB Manager to change the length
C - Lock the field back down.
Disclaimer: Since there's still a lot of hard-code in Activity/History any changes to existingg core fields has teh possibility of introducing serious problems into SalesLogix. This CAN impact LAN and/or Remotes in in unpredictable manner.
--
rjl |
|
|
|
Re: History Table Custom Field
Posted: 23 Apr 07 7:26 AM
|
fiogf49gjkf0d I'm just going to put in my .02 and suggest a diferent route..
You stated the requirement was that reps need to associate a product with each history. Instead of creating a field to store the product name (of up to length 128) or hacking existing fields (which is only asking for more trouble)... wouldn't it be more efficient (and normalized) to just add a custom field of length 12 that stores the product ID? You'll need to change the SQL that retrieves the history detail to include the product table, but that should be easy.
John G. |
|
|
|
Re: History Table Custom Field
Posted: 24 Apr 07 6:52 PM
|
fiogf49gjkf0d Hi Bob,
Can you tell me how to "unlock" the field in question? my email address is "jdsk @ hotmail . com" |
|
|
|
Re: History Table Custom Field
Posted: 25 Apr 07 6:27 AM
|
fiogf49gjkf0d Originally posted by David Joseph
Hi Bob,
Can you tell me how to "unlock" the field in question? my email address is "jdsk @ hotmail . com" |
|
Please send me an email directly from your business address.
--
rjl |
|
|
| |
|
Re: History Table Custom Field
Posted: 28 Apr 07 7:01 AM
|
fiogf49gjkf0d Just click on my posting "name" and it will take you to a page on this site where you can send me an email.
--
rjl |
|
|
|
Re: History Table Custom Field
Posted: 28 Apr 07 10:01 AM
|
fiogf49gjkf0d Originally posted by David Joseph
Hi Bob,
Can you tell me how to "unlock" the field in question? |
|
Remember, this is all unsupported. Proceed at your own risk.
1) Execute the following to unlock the history table:
update sectabledefs set userdef = 'T' where tablename = 'HISTORY'
2) Make changes to the table as necessary (increase field lengths add fields, etc)
3) Lock the table again by executing the following:
update sectabledefs set userdef = 'F' where tablename = 'HISTORY'
Have fun.
-Ryan
|
|
|
|
Re: History Table Custom Field
Posted: 28 Apr 07 10:04 AM
|
fiogf49gjkf0d Also keep in mind, this procedure to change the field length won't sync. Your best bet is to recut any remotes after a change like this. There are some tricks you can do to get it to sync but a recut is the safest route. Some things to try is bundling the field (with it's new length set) and applying it to the main database etc. |
|
|
|
Re: History Table Custom Field
Posted: 01 May 07 1:11 PM
|
fiogf49gjkf0d Thanx for your input!! we do not have remote users so its one less think to worry about  |
|
|
|