Labels

"Milestone Summary" portlet is not sorta
1
9.62 GUI installation
2
Ad
9
Adding Developer name field from Object type...
1
Admin
65
Admin Console
11
Agile
7
AlreadyInOctane
0
Analyze Assignment Load
1
AOL
2
API
13
Approval from email notification
2
Approve Time
7
Approved Budget User Data Fields
1
Assignment update using position update ...
2
Attachment with notification
2
Audit Logs
7
Audit Trail
5
Authentication
5
Autofill
2
background service restart
1
Bar chart
4
Certification
6
Change Project Name
1
CHPERPDBA@mountsinai.org
1
Clear cache issue wrt RequestRulesUserLibrary...
1
Closed Project
3
Confirmation
9
Copy_Header's_User_Data_Default_No
2
cost health icon
1
Dashboard Usability
13
Dashboards
20
Databases
7
decimals
4
Demand Management
35
department
1
deployment
8
Display info on logon page
1
Enabling Floating License
1
Export to PDF
7
exporting to PDF and Excel
7
Feature Request
68
Field Type
7
file attachment
4
Filters
10
Financial & Staffing Profile
17
Financial Summary
27
FinancialSummaryAPI
2
Github
1
Global KPI
3
Import from excel to Table component
3
in-line editing
2
Include use
11
Top Voted Ideas: Last 30 Days
API Keys - Allow for regeneration of the API Key
3
Idea ID: 2701803

Enable Import from excel to Table component

Aurobinda
Status: Delivered

Enable Import from excel to Table component

  •  

    Implemented in PPM 9.63.

    There's some pretty significant limitation as importing TC from Excel bypasses the rules - so you can decide at the TC validation level whether or not to enable Excel Import for that specific Table Component.

  •  

    Thanks for the input.

    This won't be easy to implement, as TC will typically only show a few rows that are editable, and excel will allow you to change everything at the same time - for this reason, it's much better fit at saving TC content from Excel directly in the backend, thus bypassing UI Rules.

  •  Thanks for the update. I believe, if we are managing to import the data from excel to table component and once user tries to save the date in TC/request the rules must validate from there. This way, at least the functionality would be bit easier to achieve.

  •  

    Hi All,

    I'm currently investigating into implementing this capability in a future PPM version. More precisely, it would be about exporting an existing table component to Excel (XLSX), and then importing the contents of the modified excel file back into the table component.

    The main blocker I'm facing is about UI rules: When the table component is modified programatically, the UI rules (which are client-side Javascript) will not take effect. This also applies when updating the TC through REST API by the way. This basically means that you won't be able to have any UI rule take effect when data is modified or inserted in the table component from an Excel Import.

    Is that an acceptable limitation? Do you need the ability to disable Excel Import in the Table Component Validation definition, for the cases where UI Rules cannot be ignored?

  • Our users have also asked for this capability

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.