One thing we are missing when doing migration with direct sql approach is that all table level formulas will not be automatically calculated. In the past we must reproduce the code inside our migration script to handle all formulas manually.
To help the performance, Pivotal automatically generates a bunch of stored procedures inside the ED with the following format rsp_tablename_update_formulas. Most of them have only three parameters:
@recordId binary (8) @CurrentUserId binary(8) @CurrentUserName varchar(255)
These stored procedures, we can use it out-of-the-box by calling it inside our migration script.
Unfortunately, for more complex formulas such as the ones with date related, soundex etc, Pivotal platform decided to do the calculation at the application level and pass the calculated values the stored procedures as additional parameters such as @P1, @P2, etc.
The beauty with this approach is, we only need to re-code the application level formulas and leave most of the calculation to the Pivotal auto generated stored procedures.
June 25, 2008 at 9:42 am |
Hi there,
Is there a way to include soundex on the contact search screen? This exists as an option on the windows client (ie ‘starts with’,’contains’)
I appreciate any code you can provide.
thanks
Ratan
June 25, 2008 at 9:43 am |
I meant to say include contact soundex funationality for the rich client
June 26, 2008 at 12:33 pm |
Yes – set the soundex field as desktop findable from Pivotal Toolkit