Verified Answers


If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it!  Learn more

  • State Verified Answer
  • Replies reply
    1
  • Subscribers subscribers
    12
  • Views views
    87
  • Users 0 members are here
Related
Options

Forecast User Data in the Financial Summary can be configured per Request Type and/or per Financial Summery vs Financial Data Table?

Silvio Crivellini

Hi All.

Using PPM 24.3 coming from historical PPM (installed on 2009!), there are some Forecast User Data needed for the existing "old" entity; the #11 Forecast User Data are defined to support Financial Data Table to integrate specific Request Types associated at specific Project Type.

Now in the modernization of the Customer instance, I need to define a PFM Proposal without these #11 Forecast User Data. Since the OOTB Forecast User Data are global, the #11 Forecast User Data are available also in the Financial Summary.

How can I at least hide these historical Forecast User Data from news objects ? Suitable criteria can be:

  • These (or all) Forecast User Data are available in the Financial Data Type, not in the Financial Summary or
  • These (or all) Forecast User Data are available in Financial Data Type associated with specific Request Type and/or Specific Project Type

Next image represent an example of Forecast User Data that need to be masked/hide from the new instance

 

Besr Regards, Silvio

  • Verified Answer

    +1  

    Hi Silvio,

    As you wrote, User Data fields are Global (Except validations User Data, but it's an exception). There is no way I know of to conditionally hide these UD fields only on the "new" requests. You may want to write some script to bring all that custom data into some proper FS data, and then get rid of the UD fields globally when that's an option.

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.