pm_portfolio field on pm_project table

[solonxu]

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).

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.

[Brian Dailey1]

Hi Solon,

I understand, but this is why I suggest (1) & (2).

Rather than change an OOB object (like the BR in question), if you only inactivate it (Active=false), it will still get updated by system upgrades and maintenance later on.   So what you're doing is creating your own custom copy of it to alter/customize, and preserving (not altering) the OOB version (just in an inactive state).

When you do it (customize) in this way, you will still receive the updated versions of those OOB objects, but the updates will leave it inactive and you should avoid the problem you mentioned.

But if you're still a little hesitant, just give it a try in your DEV/sandbox instance and see if that fixes your original problem.

-Brian

[solonxu]

Actually we ever did same thing before, we deactivated a BR and system upgrade re-activated it....

[Brian Dailey1]

That's odd, not supposed to work that way.   But I must say, we've probably run into the same issue causing things to break temporarily.

-Brian