04-28-2010 01:25 PM
I discovered an issue with field level security for 1-1 custom tables that were created pre-7.22 I found out that you need to add a field seccodeid & populate to custom 1-1 tables created pre 7.22 inorder for the field security to work. Now, I find that when you change the ownership at the account level, it doesn't update the seccodeid field in the custom table. Is this a defect?
------ my SQL query to check on the seccodeid between the opportunity table and custom table
select a1.seccodeid, a2.seccodeid from opportunity a1 inner join ep_opportunitycustom a2 on a1.opportunityid = a2.opportunityid where accountid = 'A6UJ9A001R8R'
----------- my result ---------- The seccodeid don't match.