pm_portfolio field on pm_project table

solonxu
Kilo Expert

‎02-09-2016 11:04 AM

I found there is a field named 'pm_portfolion' on Project table in client's instance (glide-fuji-12-23-2014__patch10-10-21-2015), but this field doesn't exist in my developer instance (glide-fuji-12-23-2014__patch11-11-18-2015).

find_real_file.png

Any idea how would this work? I guess this is the legacy field of V2 engine. It was no longer active but actually affects current business rule. Would like to know more about this.

Any suggestion would be appreciated.

Preview file
78 KB
0 Helpfuls
  • 1,542 Views
7 REPLIES 7

Brian Dailey1
Kilo Sage

‎02-09-2016 11:20 AM

Hi Solon,



We are on a slightly older version (glide-fuji-12-23-2014__patch7-hotfix5-09-01-2015_09-01-2015_1202) and do not have that field on [pm_project], however we do have a different reference field to Portfolio called 'primary_portfolio' on the project table.



Don't know if that helps any.




Thanks,


-Brian


0 Helpfuls

solonxu
Kilo Expert
In response to Brian Dailey1

‎02-09-2016 11:24 AM

Right, we do have primary_portfolio after activating PPM module. This inactive field 'pm_portfolio' caused a problem with business rule 'Add Project to Portfolio'. I cannot delete this dictionary entry either....


0 Helpfuls

Brian Dailey1
Kilo Sage
In response to solonxu

‎02-09-2016 11:51 AM

Hi Solon,



Looking at the business rules, I assume you are talking about the BR "Add Project to Portfolio" on [pm_project].   It looks like it was an oversight when they updated the code, since there is only active mention in the code to "pm_portfolio" and all others point to "primary_portfolio" as the reference field to Portfolio.



pm_portfolio.png




I would suggest trying this:


  1. Change the BR to inactive and save.
  2. Perform an Insert and Stay on this BR to create your own custom copy.
  3. Change that one piece of the script to use "primary_portfolio" instead of "pm_portfolio"
  4. Set the BR active
  5. Save



Make those changes and see how it works.



Thanks,


-Brian


Preview file
34 KB
0 Helpfuls

solonxu
Kilo Expert
In response to Brian Dailey1

‎02-09-2016 12:32 PM

Thanks Brian. I am sure your method works, but I dont really like to update system scripts. We did get problem that we updated a OOB script and system upgrade brought it back. Here I would like an explanation to this field, how does SN handle this legacy field? I will open a HI ticket for this.



Thank you for your comments anyway


0 Helpfuls